Categories
CVE-2026-45703 medium CVSS 6.4

Authorization Flaw in pimcore/pimcore (CVE-2026-45703)

Summary

Vulnerability in pimcore/pimcore (CVE-2026-45703). Risk of unauthorized operations or information disclosure. Exploitable via WordExport. Mitigation: upgrade to 2026.1.3 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.7, the WordExport export flow in bundles/WordExportBundle/src/Controller/TranslationController.php only checks the word_export feature permission and directly resolves attacker-controlled type/id input without enforcing view permission on page, snippet, email, or object elements, allowing a low-privileged backend user to export document content the user is not allowed to view. This issue is fixed in versions 11.5.17 (LTS) and 12.3.7.

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-45703 has been found in pimcore/pimcore.
Attackers can target a specific entry point like WordExport over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 6.4/10.
What to do: upgrade pimcore/pimcore to 2026.1.3 or later.
If unsure, ask your IT team or search "pimcore/pimcore CVE-2026-45703" on the vendor's site.

CVE-2026-45703 (pimcore/pimcore) — CWE-863 / CVSS v3 6.4
Attack vector: remote (network-reachable) / no user interaction
Attack surface: WordExport / word_export / view / Page
Patched: 2026.1.3 — 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

Incorrect authorization (CWE-863) exists in pimcore/pimcore. Attackers reach the vulnerable code path via WordExport.

📍 Affected scope

Check the vendor advisory for the affected versions of pimcore/pimcore. Attack surface: WordExport / word_export / view / Page.

🔥 Severity

Severity: Medium (CVSS 6.4/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 2026.1.3.

🛡️ 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 2026.1.3

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

  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":"2026.1.3"}]}]
Packagist pimcore/pimcore
[{"type":"ECOSYSTEM","events":[{"introduced":"2026.1.0"},{"fixed":"2026.1.3"}]}]

References

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