← Back
GHSA-cmwh-pvxp-8882
Cross-Site Scripting (XSS) in dompurify (GHSA-cmwh-pvxp-8882)
Summary
cross-site scripting in dompurify (GHSA-cmwh-pvxp-8882). Risk of unauthorized operations or information disclosure. Exploitable via ``uponSanitizeAttribute``. Mitigation: upgrade to `3.4.11` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **GHSA-cmwh-pvxp-8882** has been found in dompurify.
Attackers can target a specific entry point like ``uponSanitizeAttribute`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade dompurify to **3.4.11** or later.
If unsure, ask your IT team or search "dompurify GHSA-cmwh-pvxp-8882" on the vendor's site.
GHSA-cmwh-pvxp-8882 (dompurify) — CWE-79 /
Attack surface: `uponSanitizeAttribute` / `data.allowedAttributes` / `ALLOWED_ATTR` / `_parseConfig`
Patched: `3.4.11` — 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
**Cross-site scripting (XSS)** (CWE-79) exists in dompurify. Attackers reach the vulnerable code path via ``uponSanitizeAttribute`` without authentication.
📍 Affected scope
dompurify — . Attack surface: `uponSanitizeAttribute` / `data.allowedAttributes` / `ALLOWED_ATTR` / `_parseConfig`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **3.4.11**.
🛡️ 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 'dompurify' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'dompurify' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `dompurify` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade dompurify to 3.4.11ステージング環境で 3.4.11 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
dompurify
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.4.11"}]}]