# CVE-2026-55634: Pimcore: Remote Code Execution via DataObject Class-Definition Field Name

> Authenticated users can inject PHP code and SQL identifiers via DataObject field names, leading to remote code execution and schema modification.

- **Severity:** Critical 9.9 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **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:** 28 Aug 2026
- **Updated:** 28 Aug 2026
- **Also known as:** GHSA-9x44-4gxf-8c25

## What is CVE-2026-55634?

CVE-2026-55634 is a critical code injection vulnerability in pimcore, published on 28 Aug 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 11.5.19, 12.3.10, and 2026.1.6, the class-definition import endpoint /pimcore-studio/api/class/definition/configuration-view/detail/{id}/import accepts a DataObject field name that is emitted without an identifier allowlist by lib/DataObject/ClassBuilder/FieldDefinitionPropertiesBuilder.php into generated PHP properties and by models/DataObject/ClassDefinition/Helper/Dao.php into ALTER TABLE identifiers. An authenticated user with the objects permission can inject PHP syntax into the generated DataObject class, causing attacker-controlled code in generated var/classes/DataObject/.php files to run when an object of that class is instantiated, and can also inject SQL identifier content into schema-changing statements. The central models/DataObject/ClassDefinition/Data.php::setName() validation did not reject semicolons, braces, backticks, spaces, or other non-identifier characters. This issue is fixed in versions 11.5.19, 12.3.10, and 2026.1.6.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pimcore/pimcore` | Packagist | All versions | 12.3.10 |
| `pimcore/pimcore` | Packagist | All versions | 12.3.10 |
| `pimcore/pimcore` | Packagist | From 2026.1.0 | 2026.1.6 |
| `pimcore/pimcore` | Packagist | From 2026.1.0 | 2026.1.6 |

## How do I fix CVE-2026-55634?

Upgrade pimcore/pimcore to a fixed version for your release line: 12.3.10 or 2026.1.6.

## Is CVE-2026-55634 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-55634 is a critical code injection vulnerability in pimcore, published on 28 Aug 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-55634 exists.

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

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-55634/ (Markdown: https://insights.sbomify.com/CVE-2026-55634/index.md)
```

## Sources

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

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