← Back
GHSA-c2j3-45gr-mqc4
Cross-Site Scripting (XSS) in dompurify (GHSA-c2j3-45gr-mqc4)
Summary
cross-site scripting in dompurify (GHSA-c2j3-45gr-mqc4). Risk of unauthorized operations or information disclosure. Exploitable via ``CUSTOM_ELEMENT_HANDLING``. Mitigation: upgrade to `3.4.12` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **GHSA-c2j3-45gr-mqc4** has been found in dompurify.
Attackers can target a specific entry point like ``CUSTOM_ELEMENT_HANDLING`` 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.12** or later.
If unsure, ask your IT team or search "dompurify GHSA-c2j3-45gr-mqc4" on the vendor's site.
GHSA-c2j3-45gr-mqc4 (dompurify) — CWE-79 /
Attack surface: `CUSTOM_ELEMENT_HANDLING` / `CUSTOM_ELEMENT_HANDLING.tagNameCheck` / `afterSanitizeElements` / `innerHTML`
Patched: `3.4.12` — 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 ``CUSTOM_ELEMENT_HANDLING`` without authentication.
📍 Affected scope
dompurify — . Attack surface: `CUSTOM_ELEMENT_HANDLING` / `CUSTOM_ELEMENT_HANDLING.tagNameCheck` / `afterSanitizeElements` / `innerHTML`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **3.4.12**.
🛡️ 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.12ステージング環境で 3.4.12 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、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.12"}]}]
References
- web https://github.com/cure53/DOMPurify/security/advisories/GHSA-c2j3-45gr-mqc4
- web https://github.com/cure53/DOMPurify/pull/1537
- web https://github.com/cure53/DOMPurify/commit/a9ca1e537422319a557a9a2aa61f003b23b4a197
- web https://github.com/cure53/DOMPurify/releases/tag/3.4.12
- web https://github.com/advisories/GHSA-c2j3-45gr-mqc4