Vulnerability in pimcore/pimcore (CVE-2021-39170)
Summary
Vulnerability in pimcore/pimcore (CVE-2021-39170). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 10.1.2 or later.
Original description
The description as published by the source.
Pimcore is an open source data & experience management platform. Prior to version 10.1.2, an authenticated user could add XSS code as a value of custom metadata on assets. There is a patch for this issue in Pimcore version 10.1.2. As a workaround, users may apply the patch manually.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
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-2021-39170 has been found in pimcore/pimcore.
Risk of unauthorized operations or information disclosure.
What to do: upgrade pimcore/pimcore to 10.1.2 or later.
If unsure, ask your IT team or search "pimcore/pimcore CVE-2021-39170" on the vendor's site.
CVE-2021-39170 (pimcore/pimcore) — CWE-116
Attack vector: remote (network-reachable)
Patched: 10.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.
A vulnerability (CWE-116) exists in pimcore/pimcore.
Check the vendor advisory for the affected versions of pimcore/pimcore.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 10.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 10.1.2ステージング環境で 10.1.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- patch github.com
- patch github.com
- patch github.com
- patch huntr.dev
- web github.com
- web huntr.dev
- web huntr.dev