pimcore/pimcore security advisory

CVE-2026-44739: Pimcore Vulnerable to SQL Injection in Custom Reports Column Configuration

CVE-2026-44739 is a high-severity SQL injection vulnerability in the PHP package pimcore/pimcore (CVSS 8.7), published 17 July 2026. It is fixed in 2026.1.2; earlier versions are affected. Exploiting it needs a low-privilege user account.

high 8.7 published 2026-07-17 · updated 2026-07-22

Affected versions: <= 11.5.16
>= 12.0.0-RC1, <= 12.3.5
>= 2026.1.0, < 2026.1.2
Fixed in: 2026.1.2
Newest release: 2026.3.4
Severity: High · CVSS 8.7
Type: SQL injection
CWE-89
Exploited in the wild: Not on the CISA KEV list
checked 2026-11-04

Is your pimcore/pimcore version affected?

Run composer show pimcore/pimcore in your project, then enter the version. We check it against this and every other known pimcore/pimcore advisory.

Who can exploit CVE-2026-44739

Access: A normal, low-privilege user account in the app.
Interaction: A user also has to do something, such as open a link or a page the attacker prepared.

CVSS vector (scored by GitHub): CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N

Your app is only exposed if it uses the affected part of pimcore/pimcore. The advisory below says which part that is. If you are not sure, upgrade anyway: it costs less than finding out.

How to fix CVE-2026-44739 in pimcore/pimcore

Find the installed version: composer show pimcore/pimcore. If you never required it yourself, composer why pimcore/pimcore shows which package pulls it in.
Update it: composer update pimcore/pimcore --with-all-dependencies. You need 2026.1.2 or newer.
If Composer will not go that high, your composer.json constraint is holding it back. Widen it (for example "pimcore/pimcore": "^2026.1.2" if you can take that version), or upgrade the package that requires it.
Run composer audit. It reads the same advisory data and should no longer list CVE-2026-44739.
Commit composer.lock and deploy it. On the server, run composer install --no-dev from the lock file, not composer update.

If you cannot upgrade yet

General hardening for SQL injection issues while the upgrade waits. None of it replaces the fix.

Make sure user input never reaches the affected query builder or ORM method unvalidated; allow-list column and sort names.
Give the app's database user only the permissions it needs.
If your app does not use the affected feature, note that in your audit, but still plan the upgrade.

The CVE-2026-44739 advisory

Pimcore is an Open Source Data & Experience Management Platform. Prior to 11.5.17 (LTS) and 12.3.6, the columnConfigAction endpoint in bundles/CustomReportsBundle/src/Controller/Reports/CustomReportController.php passes malicious SQL configuration through CustomReportController:columnConfigAction, SqlAdapter::getColumns, SqlAdapter::buildQueryString, and Db::fetchAssociative(), allowing an attacker with the reports_config permission to use arbitrary SELECT queries, UNION statements, dangerous database functions, and error-based SQL injection to exfiltrate or manipulate database data. This issue is fixed in versions 11.5.17 (LTS) and 12.3.6.

Description from the CVE record, published by GitHub (the CVE Numbering Authority), via the NVD entry for CVE-2026-44739. Advisory title: “Pimcore Vulnerable to SQL Injection in Custom Reports Column Configuration”.

References

GitHub advisory GHSA-3234-gxc3-pq6f github.com
Fix commit 3fd7733 github.com
Pull request #19098 github.com
Release v12.3.6 github.com

Other pimcore/pimcore advisories

Need help patching or upgrading? Laskyr does PHP and Laravel security fixes and upgrades. Tell us what you run and we reply with a plan and a price.

Ask about a fix

Where this data comes from

Affected and fixed versions: the Packagist security advisories API (GitHub Advisory Database and FriendsOfPHP), the same data composer audit uses. Synced 2026-11-03.
Description, score, weakness and references: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
Exploited-in-the-wild status: the CISA Known Exploited Vulnerabilities catalog, checked 2026-11-04.
Compiled by Daniel Lasek at Laskyr from the sources above. The summary, “who can exploit it”, “how to fix it” and hardening sections are our plain-English reading of the record and are generated from it. The quoted description is the record's own text. Spot an error? Tell us.