Cross-Site Scripting (XSS) in DOMPurify (CVE-2025-15599)
Summary
Cross-site scripting in DOMPurify (CVE-2025-15599). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 3.2.7 or later.
Original description
The description as published by the source.
DOMPurify 3.1.3 through 3.2.6 and 2.5.3 through 2.5.8 contain a cross-site scripting vulnerability that allows attackers to bypass attribute sanitization by exploiting missing textarea rawtext element validation in the SAFE_FOR_XML regex. Attackers can include closing rawtext tags like in attribute values to break out of rawtext contexts and execute JavaScript when sanitized output is placed inside rawtext elements. The 3.x branch was fixed in 3.2.7; the 2.x branch was never patched.
Source: NIST National Vulnerability Database NVD
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-2025-15599 has been found in DOMPurify.
Risk of unauthorized operations or information disclosure. CVSS score: 6.1/10.
What to do: upgrade DOMPurify to 3.2.7 or later.
If unsure, ask your IT team or search "DOMPurify CVE-2025-15599" on the vendor's site.
CVE-2025-15599 (DOMPurify) — CWE-79 / CVSS v3 6.1
Attack vector: remote (network-reachable) / unauthenticated
Patched: 3.2.7 — 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.
Cross-site scripting (XSS) (CWE-79) exists in DOMPurify.
Check the vendor advisory for the affected versions of DOMPurify.
Severity: Medium (CVSS 6.1/10). Risk of unauthorized operations or information disclosure.
Update to 3.2.7.
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 'DOMPurify' . 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 'DOMPurify' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
DOMPurifyを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade DOMPurify to 3.2.7ステージング環境で 3.2.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2025-15599 node-dompurify
- Ubuntu UBUNTU-CVE-2025-15599 node-dompurify
References
- advisory disclosure@vulncheck.com
- patch disclosure@vulncheck.com
- web disclosure@vulncheck.com