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.
CVE-2026-55072
“—” beside the score: it is equal to the CVSS score beside it.
Score 8.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-13. A secondary CVSS source baseline 8.5; sources differ by 0.0.
Also known asEUVD-2026-77635 (ENISA EUVD) · GHSA-2mhj-fhvg-v428 (GitHub Security Advisories)Source: ENISA EUVD
- CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
A fix is available — apply it.
- CVSS v3
- 8.5
- EG Score
- 8.5HIGHmedium confidence
- EG Risk
- 54EG Risk 54/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity85% × 45%Impact severity (EG Severity): CVSS 8.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation40% × 40%EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 0.4%
- EPSS %ILE
- 35th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (8.5): severity, escalated by confirmed exploitation. This CVE's 8.5 is its impact severity (EG Severity), not escalated.
- EG Severity
- 8.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
August 13, 2026
Last Modified
September 16, 2026
Advisory Details (4)
Auto-updated Sep 14, 20262026.1.5
Patch available: pimcore/pimcore v2026.1.5
https://github.com/pimcore/pimcore/releases/tag/v2026.1.5commit 33a0e1887e1e (pimcore/pimcore)
Patch available: pimcore/pimcore v12.3.9 (contains commit 33a0e1887e1e)
https://github.com/pimcore/pimcore/commit/33a0e1887e1e31b4283b016ac5440c35ea5697b4[Security]: Follow up regex check and add quoting to block tables
Patch available: pimcore/pimcore v12.3.9 (PR #19177 merged 2026-06-08)
https://github.com/pimcore/pimcore/pull/19177ClassDefinition UID regex missing end anchor allows SQL injection via Block.php unquoted table name · Advisory · pimcore/pimcore · GitHub
https://github.com/pimcore/pimcore/security/advisories/GHSA-2mhj-fhvg-v428Vendor Advisories for CVE-2026-55072(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(2)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| composer | pimcore/pimcore @ 2026.1.5 (fixes >= 2026.1.0, <= 2026.1.4) | — | ghsa |
| composer | pimcore/pimcore @ 12.3.9 (fixes < 12.3.9) | — | ghsa |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(1 across 1 ecosystem)
Packagist(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| pimcore/pimcore | 10.0.8 ... v6.9.6 (324 versions) |
| — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 45× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
- 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-11-01 07:44 UTCGHSA enrichmentGHSA-2mhj-fhvg-v428 · GitHub severity HIGH · GitHub CVSS 8.5
- 2026-11-01 07:44 UTCEG score recompute
- 2026-11-01 07:11 UTCEG score recompute
- 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-25 14:19 UTCEG score recompute
- 2026-10-24 17:21 UTCEG score recompute
- 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-10-18 03:30 UTCEG score recompute
- 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-10-17 03:34 UTCEG score recompute
- 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
Show 53 moreShow fewer
- 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-10-12 15:56 UTCEG score recompute
- 2026-10-11 19:39 UTCEG score recompute
- 2026-10-11 16:54 UTCEG score recompute
- 2026-10-11 14:17 UTCEG score recompute
- 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-10-07 01:21 UTCEG score recompute
- 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-10-06 13:27 UTCEG score recompute
- 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-10-05 14:39 UTCEG score recompute
- 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-10-03 19:50 UTCEG score recompute
- 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-10-02 19:27 UTCEG score recompute
- 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-10-02 07:35 UTCEG score recompute
- 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-09-30 21:48 UTCEG score recompute
- 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-09-29 04:07 UTCEG score recompute
- 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-09-28 00:50 UTCEG score recompute
- 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-09-27 09:45 UTCEG score recompute
- 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-09-25 03:34 UTCEG score recompute
- 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-09-23 20:50 UTCEG score recompute
- 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-09-22 21:01 UTCEG score recompute
- 2026-09-22 04:15 UTCEG score recompute
- 2026-09-21 03:49 UTCEG score recompute
- 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-09-20 01:07 UTCEG score recompute
- 2026-09-19 01:12 UTCEG score recompute
- 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-09-18 01:26 UTCEG score recompute
- 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-09-17 01:39 UTCEG score recompute
- 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-09-16 10:33 UTCEG score recompute
- 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-09-14 18:37 UTCEG score recompute
- 2026-09-14 17:56 UTCEG score recompute
- 2026-08-13 13:52 UTCEG score recomputeFirst assessed: 8.5 HIGH
Related CVEs(same product + same CWE)
Same product
10 shownPackagist:pimcore/pimcore
Frequently asked(5)
What is CVE-2026-55072?
When was the CVE record for CVE-2026-55072 published?
Is CVE-2026-55072 actively exploited?
What is the CVSS score of CVE-2026-55072?
How do I remediate CVE-2026-55072?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-55072
Is Your Infrastructure Affected by CVE-2026-55072?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.