Security readout for executives and security teams
Plain-English summary
An authenticated Pimcore user with the objects permission can submit a malicious DataObject field name that becomes server-side PHP code and may also manipulate database statements. When the affected class is instantiated, injected code can execute, threatening data confidentiality, integrity, and availability. Fixed releases are available.
Executive priority
Treat this as an immediate upgrade priority for affected Pimcore systems. Although authentication is required and active exploitation is not documented, a permitted or compromised account could execute server-side code. Prioritize externally reachable administration interfaces and environments containing sensitive data, then remediate all remaining affected instances promptly.
Technical view
The import endpoint fails to constrain field names to safe identifiers. The value enters generated PHP properties and ALTER TABLE identifiers, enabling PHP syntax injection and SQL identifier injection. Affected versions are below 11.5.19; 12.0.0-RC1 through 12.3.9; and 2026.1.0 through 2026.1.5.
Likely exposure
Exposure exists on Pimcore versions matching the documented affected ranges. Exploitation requires an authenticated account with the objects permission and access to the class-definition import endpoint. Risk is greatest where such accounts are broadly assigned, weakly protected, or compromised.
Exploitation context
The CVSS 9.9 assessment reflects network reachability, low complexity, low privileges, no user interaction, and severe cross-scope impact. The supplied evidence does not identify active exploitation, and the bundle's KEV flag is false. That absence does not establish that exploitation has never occurred.
Researcher notes
The vulnerability combines CWE-94 code injection with CWE-89 SQL injection risk. The central validation gap propagates through both PHP class generation and schema-changing SQL construction. Sources establish code execution when an affected class is instantiated, but do not document active attacks or the precise consequences of SQL identifier injection.
Mitigation direction
- Upgrade Pimcore 11 to 11.5.19 or later, 12 to 12.3.10 or later, and 2026.1 to 2026.1.6 or later.
- Until upgraded, restrict class-definition imports and objects permission to trusted administrators, following vendor guidance.
- Review objects-permission assignments and remove access that is not operationally required.
- Preserve relevant application, authentication, and schema-change logs before remediation and investigation.
Validation and detection
- Inventory every Pimcore instance and compare its exact version with the documented affected ranges.
- Confirm which accounts and roles possess the objects permission and can access class-definition imports.
- Inspect DataObject field names for characters outside expected PHP and SQL identifier conventions.
- Review generated DataObject PHP files and schema-change records for unauthorized or anomalous modifications.
- After upgrading, verify field-name validation rejects characters outside the permitted identifier format.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-55634 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.9 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H3.16GitHub_MVulnerability scoring details
Base CVSS 3.1 score
9.9CriticalVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/pimcore/pimcore/security/advisories/GHSA-9x44-4gxf-8c25CVE reference, GitHub_M · x_refsource_CONFIRM
- https://github.com/pimcore/pimcore/pull/19183CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/pimcore/pimcore/commit/a4f8c3cfee58b7d5fe4873d67782eff58dae9b9dCVE reference, GitHub_M · x_refsource_MISC
- https://github.com/advisories/GHSA-r2f4-ff2p-xc64CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/pimcore/pimcore/releases/tag/v2026.1.6CVE reference, GitHub_M · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Special Elements used in an SQL Command
Improper Neutralization of Special Elements used in an SQL Command represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
CWE mapping pending import
This CVE carries a CWE mapping that will resolve to a full Glexia CWE intelligence page after the official CWE import is complete.