Answer in brief
CVE-2026-55416 records a High severity (CVSS 8.8) vulnerability in Pimcore: SQL Injection in Mautic Custom Reports Bundle Due to Direct Concatenation of User-Controlled Configuration Fields Without Parameterization. The current sources do not mark it as known exploited. The current feed maps pimcore/pimcore (composer), pimcore/pimcore (composer), pimcore/pimcore (composer), pimcore/pimcore (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 8.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps pimcore/pimcore (composer), pimcore/pimcore (composer), pimcore/pimcore (composer), pimcore/pimcore (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| pimcore/pimcorecomposer | >=2026.1.0,<=2026.1.5 | 2026.1.6 |
| pimcore/pimcorecomposer | >=12.0.0-RC1,<=12.3.9 | 12.3.10 |
| pimcore/pimcorecomposer | <11.5.18 | 11.5.19 |
| pimcore/pimcoregeneric | < 11.5.19 || >= 12.0.0, < 12.3.10 || >= 2026.1.0, < 2026.1.6 | Not reported |
| pimcore/pimcorepackagist | >=2026.1.0 <2026.1.6 | 2026.1.6 |
| pimcore/pimcorepackagist | >=12.0.0-RC1 <12.3.10 | 12.3.10 |
| pimcore/pimcorepackagist | >=0 <11.5.19 | 11.5.19 |
Published upstream
Sep 14, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 14, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 10, 2026
Pimcore is an Open Source Data & Experience Management Platform. Prior to 11.5.19, 12.3.10, and 2026.1.6, an authenticated user with reports_config permission can place attacker-controlled SQL fragments in the sql, from, where, and groupby fields of a Custom Reports configuration processed by bundles/CustomReportsBundle/src/Tool/Adapter/Sql.php. The buildQueryString() method concatenates these values into a database query, while a blacklist omits dangerous constructs such as additional data-manipulation statements, comments, subqueries, and multiple statements. The getData() method also previously interpolated offset and limit values into a LIMIT clause without integer casting. Executing the configured report reaches fetchAllAssociative() with the constructed query and can disclose, modify, or delete arbitrary database data. This issue is fixed in versions 11.5.19, 12.3.10, and 2026.1.6.
Quoted source text, attributed separately from HOL analysis.