CVE-2026-55634 json
Pimcore: Remote Code Execution via DataObject Class-Definition Field Name
published 2026-08-28 2 mo ago modified 2026-09-09 1 mo ago also EUVD-2026-67871 , GHSA-9x44-4gxf-8c25
- cvss
- 9.9
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 51%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- packagist pimcore/pimcore 12.3.10, 2026.1.6
- pimcore pimcore 11.5.19, 12.3.10, 2026.1.6
- github.com/pimcore/pimcore@a4f8c3c commit
- github.com/pimcore/pimcore#19183 pull request
- github.com/pimcore/pimcore/releases/tag/v2026.1.6 release
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- total
- Assessed
- 2 mo ago
Exploit prediction
0.65% chance of exploitation in the next 30 days, higher than 51% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/advisories/GHSA-r2f4-ff2p-xc64 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 9.9 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H |
| GitHub | 3.1 | 9.9 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | pimcore/pimcore | <12.3.10 >=2026.1.0, <2026.1.6 |
12.3.10 2026.1.6 |
Affected products
- pimcore pimcore
Classification
References
-
github.com
/pimcore/pimcore/pull/19183
web
-
github.com
/pimcore/pimcore/commit/a4f8c3cfee58b7d5fe4873d67782eff58dae9b9d
web
-
github.com
/advisories/GHSA-r2f4-ff2p-xc64
exploit
-
github.com
/pimcore/pimcore/security/advisories/GHSA-9x44-4gxf-8c25
web
-
github.com
/pimcore/pimcore/releases/tag/v2026.1.6
web
-
github.com
/pimcore/pimcore
package
Sources
- CVE List CVE-2026-55634
- GitHub Advisory GHSA-9x44-4gxf-8c25
- NVD CVE-2026-55634
Fencer Vulns 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.