# 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.

- **Severity:** High 8.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Sep 2026
- **Updated:** 14 Sep 2026
- **Also known as:** GHSA-2mhj-fhvg-v428

## 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.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command), CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2026-55072?

4 open source packages ship an affected version, including pimcore/pimcore.


| Package | Ecosystem | 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.

## Is CVE-2026-55072 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-55072 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-55072 and fix it if it is affected.

What it is: 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-55072 exists.

Affected packages and fixed versions:
- pimcore/pimcore (Packagist): affected all versions; fixed in 12.3.9
- pimcore/pimcore (Packagist): affected all versions; fixed in 12.3.9
- pimcore/pimcore (Packagist): affected from 2026.1.0; fixed in 2026.1.5
- pimcore/pimcore (Packagist): affected from 2026.1.0; fixed in 2026.1.5

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-55072/ (Markdown: https://insights.sbomify.com/CVE-2026-55072/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-55072
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-55072
- OSV: https://osv.dev/vulnerability/CVE-2026-55072

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-55072/
Summaries are generated and may contain mistakes; the official description above is the record.