CVE-2026-55072 json
Pimcore: ClassDefinition UID regex missing end anchor allows SQL injection via Block.php unquoted table name
published 2mo ago modified last mo. also EUVD-2026-77635 , GHSA-2mhj-fhvg-v428
- cvss
- 8.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 35%
- public exploits
- 0
- none known
Summary
Pimcore is an Open Source Data & Experience Management Platform. Prior to 2026.1.5, an authenticated user with the objects permission can submit a malicious ClassDefinition UID because the name and ID validation expressions in models/DataObject/ClassDefinition.php validate only the beginning of each value. When a data object of that class containing a Block field is loaded, Block::load in models/DataObject/ClassDefinition/Data/Block.php incorporates the stored class ID into an unquoted object table identifier, allowing the UID to supply SQL syntax. The resulting query can read or modify arbitrary Pimcore database tables, including disclosure of password hashes, and the flaw represents an incomplete validation hardening because earlier work added a start anchor without enforcing the end of the identifier. This issue is fixed in version 2026.1.5.
Patch / fix
- packagist pimcore/pimcore 12.3.9, 2026.1.5
- pimcore pimcore 2026.1.5
- github.com/pimcore/pimcore@33a0e18 commit
- github.com/pimcore/pimcore#19177 pull request
- github.com/pimcore/pimcore/releases/tag/v2026.1.5 release
Is CVE-2026-55072 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- last mo.
Exploit prediction
0.41% chance of exploitation in the next 30 days, higher than 35% of all scored CVEs (FIRST EPSS, 2026-11-11).
Exploits and checks
- github.com https://github.com/pimcore/pimcore/security/advisories/GHSA-2mhj-fhvg-v428 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N |
| GitHub | 3.1 | 8.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | pimcore/pimcore | >=2026.1.0, <2026.1.5 <12.3.9 |
2026.1.5 12.3.9 |
Affected products
- pimcore pimcore
Classification
References
Sources
- CVE List CVE-2026-55072
- GitHub Advisory GHSA-2mhj-fhvg-v428
- NVD CVE-2026-55072
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.