CVE-2026-55416

Pimcore: SQL Injection in Custom Reports via Malicious Report Configuration

A SQL injection vulnerability exists in the Custom Reports bundle (bundles/CustomReportsBundle/src/Tool/Adapter/Sql.php:84-135). An authenticated attacker with reports_config permission can inject arbitrary SQL via the report configuration fields (sql, from, where, groupby), which are directly concatenated into SQL queries without parameterization. The only protection is a regex blacklist that checks for ALTER|CREATE|DROP|RENAME|TRUNCATE|UPDATE|DELETE keywords, which is trivially bypassable, it does not block INSERT, UNION SELECT, LOAD_FILE(), INTO OUTFILE, stacked queries, subqueries, or MySQL comment injection (/*!*/). Exploitation allows reading, modifying, or deleting all data in the database, leading to complete data compromise.

Additionally, the LIMIT clause at line 51 directly interpolates $offset and $limit without integer casting, creating a secondary injection point.

Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access. Typical impact: data disclosure or modification.

CVE-2026-55416 has a CVSS score of 8.8 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2026.1.6, 12.3.10, 11.5.19); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

Versions 2026.1.6, 12.3.10, 11.5.19.

1. What is CVE-2026-55416? CVE-2026-55416 is a high-severity SQL injection vulnerability in pimcore/pimcore (composer), affecting versions >= 2026.1.0, <= 2026.1.5. It is fixed in 2026.1.6, 12.3.10, 11.5.19. Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access.
2. How severe is CVE-2026-55416? CVE-2026-55416 has a CVSS score of 8.8 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of pimcore/pimcore are affected by CVE-2026-55416? pimcore/pimcore (composer) versions >= 2026.1.0, <= 2026.1.5 is affected.
4. Is there a fix for CVE-2026-55416? Yes. CVE-2026-55416 is fixed in 2026.1.6, 12.3.10, 11.5.19. Upgrade to this version or later.
5. Is CVE-2026-55416 exploitable, and should I be worried? Whether CVE-2026-55416 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-55416 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-55416?
   • Upgrade pimcore/pimcore to 2026.1.6 or later
   • Upgrade pimcore/pimcore to 12.3.10 or later
   • Upgrade pimcore/pimcore to 11.5.19 or later