Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-55072 high CVSS 8.5

Vulnerability in pimcore/pimcore (CVE-2026-55072)

Summary

Vulnerability in pimcore/pimcore (CVE-2026-55072). Confidential information can be exposed externally. Exploitable via objects. Mitigation: upgrade to 12.3.9 or later.

Original description

The description as published by the source.

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:

if (!preg_match('/^[a-zA-Z]\w+/', $this->getName())) {
    throw new Exception(sprintf('Invalid name for class definition: %s', $this->getName()));
}

if (!preg_match('/^[a-zA-Z0-9]([a-zA-Z0-9_]+)?/', $this->getId())) {
    throw new Exception(sprintf('Invalid ID `%s` for class definition %s', $this->getId(), $this->getName()));
}

Both patterns are missing a trailing $ anchor. Without it, preg_match 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:

if (!preg_match('/^[a-zA-Z]\w*$/', $key)) {   // has $ — correct
    return true;
}

3. Unquoted classId concatenation i…

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-55072 has been found in pimcore/pimcore.
Attackers can target a specific entry point like objects over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.5/10.
What to do: upgrade pimcore/pimcore to 12.3.9 or later.
If unsure, ask your IT team or search "pimcore/pimcore CVE-2026-55072" on the vendor's site.

CVE-2026-55072 (pimcore/pimcore) — CWE-20 / CVSS v3 8.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: objects / dbe1d131e4 / preg_match / lowpriv
Patched: 12.3.9 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-20) exists in pimcore/pimcore. Attackers reach the vulnerable code path via objects.

📍 Affected scope

Check the vendor advisory for the affected versions of pimcore/pimcore. Attack surface: objects / dbe1d131e4 / preg_match / lowpriv.

🔥 Severity

Severity: High (CVSS 8.5/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 12.3.9.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'pimcore/pimcore' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'pimcore/pimcore' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で pimcore/pimcore を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade pimcore/pimcore to 12.3.9

    ステージング環境で 12.3.9 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

composer pimcore/pimcore
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"12.3.9"}]}]
Packagist pimcore/pimcore
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"12.3.9"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details