Authorization Flaw in pimcore/pimcore (CVE-2026-45704)
Summary
Vulnerability in pimcore/pimcore (CVE-2026-45704). Risk of unauthorized operations or information disclosure. Exploitable via CustomReports. Mitigation: upgrade to 2026.1.2 or later.
Original description
The description as published by the source.
Pimcore is an Open Source Data & Experience Management Platform. Prior to 11.5.17 (LTS) and 12.3.6, CustomReports uses inconsistent authorization between the report listing endpoint and the report detail endpoint in bundles/CustomReportsBundle/src/Controller/Reports/CustomReportController.php and bundles/CustomReportsBundle/src/Tool/Config/Listing/Dao.php, allowing a low-privileged backend user with the reports permission to directly request an unshared report such as poc-secret-report by name and read report name, grouping information, display and icon metadata, data source configuration, column configuration, and sharing settings even when shareGlobally is false. This issue is fixed in versions 11.5.17 (LTS) and 12.3.6.
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-45704 has been found in pimcore/pimcore.
Attackers can target a specific entry point like CustomReports over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade pimcore/pimcore to 2026.1.2 or later.
If unsure, ask your IT team or search "pimcore/pimcore CVE-2026-45704" on the vendor's site.
CVE-2026-45704 (pimcore/pimcore) — CWE-863
Attack surface: CustomReports / reports / reports_config / data
Patched: 2026.1.2 — 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.
Incorrect authorization (CWE-863) exists in pimcore/pimcore. Attackers reach the vulnerable code path via CustomReports.
Check the vendor advisory for the affected versions of pimcore/pimcore. Attack surface: CustomReports / reports / reports_config / data.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 2026.1.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
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
-
1Identify exposure identify
grep -r 'pimcore/pimcore' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
pimcore/pimcoreを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade pimcore/pimcore to 2026.1.2ステージング環境で 2026.1.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- patch github.com
- patch github.com
- web github.com
- web github.com