CVE-2026-55416: Pimcore · SQL Injection in Custom Reports via Malicious Report Configuration
Affects pimcore/pimcoreSource GCVE Database
Not known to be exploited · CVSS 8.8 High : upgrade to 2026.1.6 soon.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 50% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2026.1.6, 12.3.10, 11.5.19
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 10 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade pimcore/pimcore to 2026.1.6; pimcore/pimcore to 12.3.10; pimcore/pimcore to 11.5.19.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Packagistpimcore/pimcore | Affected
| Fixed in
|
| Packagistpimcore/pimcore | Affected
| Fixed in
|
| Packagistpimcore/pimcore | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in Pimcore versions 2026.1.6, 12.3.10, and 11.5.19. Users should upgrade to these versions to remediate the vulnerability. Until patched, restrict 'reports_config' permission to highly trusted administrators only. Deploy WAF rules to block requests to '/admin/bundle/customreports/custom-report/update' containing SQL keywords in the 'configuration' parameter. Replace the vulnerable SQL adapter with a parameterized query builder that uses whitelists for table names, parameterized queries for user input, and integer casting for LIMIT/OFFSET values.
Description
Pimcore contains a SQL injection vulnerability in its Custom Reports bundle that allows an authenticated user with 'reports_config' permission to inject arbitrary SQL via report configuration fields. The vulnerability arises because user input is concatenated directly into SQL queries without proper parameterization, and the existing regex blacklist is insufficient to block many dangerous SQL constructs. Exploitation can lead to full database compromise, including reading, modifying, or deleting data. Patches are available in versions 2026.1.6, 12.3.10, and 11.5.19. Mitigations include restricting permissions, deploying WAF rules, and replacing the vulnerable SQL adapter with a parameterized query builder.
References
- github.com/pimcore/pimcore/security/advisories/GHSA-23rh-xw42-fq82 (opens in a new tab)
- github.com/pimcore/pimcore (opens in a new tab)
- github.com/pimcore/pimcore/releases/tag/v11.5.19 (opens in a new tab)
- github.com/pimcore/pimcore/releases/tag/v12.3.10 (opens in a new tab)
- github.com/pimcore/pimcore/releases/tag/v2026.1.6 (opens in a new tab)