CVE-2026-55072 Pimcore: ClassDefinition UID regex missing end anchor allows SQL injection via Block.php unquoted table name
Authenticated users can inject SQL via malicious ClassDefinition UIDs to read or modify database tables, including password hashes.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-55072?
CVE-2026-55072 is a high-severity SQL injection vulnerability in pimcore, published on 14 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
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.
Which versions are affected by CVE-2026-55072?
4 open source packages ship an affected version, including pimcore/pimcore.
| Package | Affected | Fixed in |
|---|---|---|
pimcore/pimcore Packagist | All versions | 12.3.9 |
pimcore/pimcore Packagist | All versions | 12.3.9 |
pimcore/pimcore Packagist | From 2026.1.0 | 2026.1.5 |
pimcore/pimcore Packagist | From 2026.1.0 | 2026.1.5 |
How do I fix CVE-2026-55072?
Upgrade pimcore/pimcore to a fixed version for your release line: 12.3.9 or 2026.1.5.
Use parameterised queries everywhere and never build SQL by joining strings. Upgrade affected software first; a web application firewall only buys time. More about SQL injection.
Is CVE-2026-55072 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-55072 exists.
Sources
Also known as GHSA-2mhj-fhvg-v428.