CVE-2026-55072

HIGHPre-NVD 8.58.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (32nd percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
8.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 8.5Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
8.5
EG Score
8.5HIGHmedium confidence
EG Risk
54
EG Risk 54/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity85% × 45%
Exploitation40% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
32nd
KEV
Not listed

CISA SSVCTrack 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). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 13, 2026

Last Modified

September 16, 2026

Advisory Details (4)

Auto-updated Sep 14, 2026
🔬 Proof of concept available. Patch available. Sources: github_pr, github_commit, github_release, github.
github_release Patch Available

2026.1.5

Patch available: pimcore/pimcore v2026.1.5

https://github.com/pimcore/pimcore/releases/tag/v2026.1.5
github_commit Patch Available

commit 33a0e1887e1e (pimcore/pimcore)

Patch available: pimcore/pimcore v12.3.9 (contains commit 33a0e1887e1e)

https://github.com/pimcore/pimcore/commit/33a0e1887e1e31b4283b016ac5440c35ea5697b4
github_pr Patch Available

[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/19177
github Patch Available🟡 PoC Available

ClassDefinition 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-v428

Vendor 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.

Affected Packages

(1 across 1 ecosystem)
Packagist(1)
PackageVulnerable rangeFix by version rangeDependents
pimcore/pimcore10.0.8 ... v6.9.6 (324 versions)
  • 2026.1.0 up to 2026.1.5: fixed in 2026.1.5
  • every version up to 12.3.9: fixed in 12.3.9
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 12× in last 7d / 36× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-10-05 14:39 UTCEG score recompute
  2. 2026-10-04 23:22 UTCEPSS rescore
  3. 2026-10-03 19:50 UTCEG score recompute
  4. 2026-10-03 14:26 UTCEPSS rescore
  5. 2026-10-02 19:27 UTCEG score recompute
  6. 2026-10-02 17:56 UTCEPSS rescore
  7. 2026-10-02 07:35 UTCEG score recompute
  8. 2026-10-01 19:50 UTCEPSS rescore
  9. 2026-09-30 21:48 UTCEG score recompute
  10. 2026-09-30 15:03 UTCEPSS rescore
  11. 2026-09-29 15:22 UTCEPSS rescore
  12. 2026-09-29 04:07 UTCEG score recompute
  13. 2026-09-28 13:51 UTCEPSS rescore
  14. 2026-09-28 00:50 UTCEG score recompute
  15. 2026-09-27 13:48 UTCEPSS rescore
  16. 2026-09-27 09:45 UTCEG score recompute
  17. 2026-09-26 15:59 UTCEPSS rescore
  18. 2026-09-25 03:34 UTCEG score recompute
  19. 2026-09-24 14:04 UTCEPSS rescore
  20. 2026-09-23 20:50 UTCEG score recompute
  21. 2026-09-23 17:54 UTCEPSS rescore
  22. 2026-09-22 21:01 UTCEG score recompute
  23. 2026-09-22 04:15 UTCEG score recompute
  24. 2026-09-21 03:49 UTCEG score recompute
  25. 2026-09-20 20:16 UTCEPSS rescore
Show 12 more
  1. 2026-09-20 01:07 UTCEG score recompute
  2. 2026-09-19 01:12 UTCEG score recompute
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-18 01:26 UTCEG score recompute
  5. 2026-09-17 19:31 UTCEPSS rescore
  6. 2026-09-17 01:39 UTCEG score recompute
  7. 2026-09-16 14:08 UTCEPSS rescore
  8. 2026-09-16 10:33 UTCEG score recompute
  9. 2026-09-16 05:15 UTCEPSS rescore
  10. 2026-09-14 18:37 UTCEG score recompute
  11. 2026-09-14 17:56 UTCEG score recompute
  12. 2026-08-13 13:52 UTCEG score recompute

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-55072?
CVE-2026-55072 is a high vulnerability published on August 13, 2026. 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…
When was CVE-2026-55072 disclosed?
CVE-2026-55072 was first published on August 13, 2026, with the most recent update on September 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-55072 actively exploited?
CVE-2026-55072 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (32nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-55072?
CVE-2026-55072 has a CVSS base score of 8.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-55072?
A fix for CVE-2026-55072 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-55072 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-55072

Explore →

Is Your Infrastructure Affected by CVE-2026-55072?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs