Pimcore: ClassDefinition UID regex missing end anchor allows SQL injection via Block.php unquoted table name
CVE-2026-55072GHSA-2mhj-fhvg-v428
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (pimcore/pimcore 2026.1.5, 12.3.9), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Packagist pimcore/pimcore
- Affected
- >= 2026.1.0, <= 2026.1.4< 12.3.9
- Fixed in
- 2026.1.5, 12.3.9
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-2mhj-fhvg-v428 lists affected ranges: Packagist pimcore/pimcore >=2026.1.0 =0 <12.3.9 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-2mhj-fhvg-v428 lists affected ranges: Packagist pimcore/pimcore >=2026.1.0 =0 <12.3.9
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 8.5 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N
- EPSS
- CVE-2026-55072: 0.41% estimated exploitation activity in the next 30 days; percentile 35.22 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Summary A missing end anchor ($) in the ClassDefinition UID validation regex allows an authenticated user with the objects permission to create a class with a malicious UID containing SQL. When a data object of that class is later loaded, Block.php concatenates the raw classId directly into a SQL query without quoting, executing the injected payload. This is an incomplete fix from commit dbe1d131e4 which added a leading ^ anchor but omitted the trailing $. Details 1. Missing end anchor in ClassDefinition UID validation models/DataObject/ClassDefinition.php lines 1148-1154: Both patterns are missing a trailing $ anchor. Without it, pregmatch only checks that the string STARTS with a valid identifier — it does not assert end-of-string. A UID of 1 UNION SELECT password FROM users-- passes because the regex matches 1 at the start and ignores the rest. Compare with the correct pattern used by Fieldcollection in models/DataObject/Fieldcollection/Definition.php line 268: 3. Unquoted classId…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from ghsa record GHSA-2mhj-fhvg-v428
- Revision 1 · created ·
Published from osv record GHSA-2mhj-fhvg-v428
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-55072 Advisory: Pimcore: ClassDefinition UID regex missing end anchor allows SQL injection via Block.php unquoted table name IDs: CVE-2026-55072, GHSA-2mhj-fhvg-v428 Record: https://patchnext.com/advisories/cve-2026-55072 (revision 2, source checked 26 Oct 2026, 14:50 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: High (CVSS 8.5) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: pimcore/pimcore 2026.1.5, 12.3.9. A vendor fix does not mean a deployment is fixed. ## Affected components - Packagist pimcore/pimcore: affected >= 2026.1.0, <= 2026.1.4; < 12.3.9; fixed in 2026.1.5, 12.3.9 ## Suggested inspection (read-only) - Packagist pimcore/pimcore: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on pimcore/pimcore. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/GHSA-2mhj-fhvg-v428 (OSV record GHSA-2mhj-fhvg-v428 lists affected ranges: Packagist pimcore/pimcore >=2026.1.0 =0 <12.3.9 (fixed)) - Verified: https://github.com/advisories/GHSA-2mhj-fhvg-v428 (GitHub-reviewed advisory GHSA-2mhj-fhvg-v428 lists affected ranges: Packagist pimcore/pimcore >=2026.1.0 =0 <12.3.9) Commands are suggestions: review each one before running it.
Loading voting…