Vulnerability in pimcore/pimcore (CVE-2026-45260)
Summary
Vulnerability in pimcore/pimcore (CVE-2026-45260). Data can be tampered with by attackers. Exploitable via MOVE. Mitigation: upgrade to 11.5.17 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, Pimcore's WebDAV asset endpoint exposes a MOVE operation through /asset/webdav{path} without an authentication plugin in bundles/CoreBundle/src/Controller/WebDavController.php, and models/Asset/WebDAV/Tree.php performs asset mutation and deletion through models/Asset.php before checking a current Pimcore user or the rename, delete, create, or publish permissions, allowing unauthorized asset deletion, moves, or overwrites. 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-45260 has been found in pimcore/pimcore.
Attackers can target a specific entry point like MOVE over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 8.1/10.
What to do: upgrade pimcore/pimcore to 11.5.17 or later.
If unsure, ask your IT team or search "pimcore/pimcore CVE-2026-45260" on the vendor's site.
CVE-2026-45260 (pimcore/pimcore) — CWE-862 / CVSS v3 8.1
Attack vector: remote (network-reachable) / no user interaction
Attack surface: MOVE / rename / delete / create
Patched: 11.5.17 — 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.
A vulnerability (CWE-862) exists in pimcore/pimcore. Attackers reach the vulnerable code path via MOVE.
Check the vendor advisory for the affected versions of pimcore/pimcore. Attack surface: MOVE / rename / delete / create.
Severity: High (CVSS 8.1/10). Data can be tampered with by attackers.
Update to 11.5.17.
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 11.5.17ステージング環境で 11.5.17 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
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