CVE-2026-55634
CRITICALDescription
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.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Exploit Intelligence
Low risk: more likely to be exploited than 37% of all known CVEs.
References
Related Vulnerabilities
Other CWE-89 (SQL Injection) vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2014-3704 | High | 7.5 | 100% | - | Fix |
| CVE-2015-7297 | High | 7.5 | 100% | - | - |
| CVE-2024-29824 | High | 8.8 | 100% | KEV | Fix |
| CVE-2023-34362 | Critical | 9.8 | 100% | KEV + Ransom | Fix |
| CVE-2019-7481 | High | 7.5 | 100% | KEV + Ransom | Fix |
| CVE-2024-29826 | High | 8.8 | 100% | - | Fix |
Common questions
How do I fix CVE-2026-55634?
No published fix for CVE-2026-55634 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-55634 being actively exploited?
Not that we know of. CVE-2026-55634 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.45% is the estimated probability that it will be exploited in the next 30 days. That is higher than 37% of all scored CVEs.
How severe is CVE-2026-55634?
CVE-2026-55634 has a CVSS v3 base score of 9.9, rated critical. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-55634
Markdown
[](https://tridentstack.com/cve/CVE-2026-55634)HTML
<a href="https://tridentstack.com/cve/CVE-2026-55634"><img src="https://tridentstack.com/cve/badge/CVE-2026-55634.svg" alt="CVE-2026-55634"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-08-28.