{"answers":{"affected":"2 open source packages ship an affected version, including dompurify. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-47423 exists.","fix":"Upgrade dompurify to 3.4.5 or later.","what":"CVE-2026-47423 is a high-severity cross-site scripting vulnerability in cure53 DOMPurify, published on 14 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-47423 and fix it if it is affected.\n\nWhat it is: CVE-2026-47423 is a high-severity cross-site scripting vulnerability in cure53 DOMPurify, published on 14 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-47423 exists.\n\nAffected packages and fixed versions:\n- dompurify (npm): affected from 3.4.4; fixed in 3.4.5\n- dompurify (npm): affected from 3.4.4; fixed in 3.4.5\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-47423/ (Markdown: https://insights.sbomify.com/CVE-2026-47423/index.md)","id":"CVE-2026-47423","markdown":"https://insights.sbomify.com/CVE-2026-47423/index.md","name":"CVE-2026-47423","record":{"aliases":["DEBIAN-CVE-2026-47423","GHSA-87xg-pxx2-7hvx","UBUNTU-CVE-2026-47423"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"JavaScript HTML sanitizer","requires_auth":"none","summary":"DOMPurify fails to sanitize selectedcontent elements, allowing attackers to inject XSS payloads that execute in the victim's browser.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"dompurify","vendor":"cure53"}],"cvss":{"score":8.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"DOMPurify is a DOM-only cross-site scripting sanitizer for HTML, MathML, and SVG. In 3.4.4, DOMPurify allowed selectedcontent by default, allowing browsers to re-clone an XSS payload after sanitization so that unsanitized markup inside \u003cselectedcontent\u003e is returned. This issue is fixed in version 3.4.5.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":"2026-06-03","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-06-03T17:20:04Z","kind":"github_poc","ref":"https://github.com/Galaxy-sc/CVE-2026-47423-dompurify-xss-detector","stars":0,"title":null}],"tier":"weaponised"},"has_fix":true,"headline":"DOMPurify XSS via `selectedcontent` re-clone","id":"CVE-2026-47423","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"xss","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"OpenAM Authenticated RCE via Groovy Sandbox Escape","id":"CVE-2026-47424"},"packages":[{"ecosystem":"npm","fixed":["3.4.5"],"introduced":["3.4.4"],"last_affected":[],"package":"dompurify","purl":null,"source":"GHSA-87xg-pxx2-7hvx"},{"ecosystem":"npm","fixed":["3.4.5"],"introduced":["3.4.4"],"last_affected":[],"package":"dompurify","purl":"pkg:npm/dompurify","source":"GHSA-87xg-pxx2-7hvx"}],"prev":{"headline":"Frappe: Unrestricted API access to save_report","id":"CVE-2026-47422"},"products":["DOMPurify"],"published":"2026-07-14","related":[{"cvss_score":10,"headline":"DOMPurify nesting-based mXSS","id":"CVE-2024-47875","kev_date_added":null,"published":"2024-10-11"},{"cvss_score":9.1,"headline":"DOMPurify vulnerable to tampering by prototype polution","id":"CVE-2024-48910","kev_date_added":null,"published":"2024-10-31"},{"cvss_score":7.3,"headline":"Tampering by prototype polution in DOMPurify","id":"CVE-2024-45801","kev_date_added":null,"published":"2024-09-16"},{"cvss_score":6.3,"headline":"DOMPurify IN_PLACE Sanitization Bypass via Attached Shadow Root Inside \u003ctemplate\u003e.content","id":"CVE-2026-49978","kev_date_added":null,"published":"2026-07-14"},{"cvss_score":6.1,"headline":"DOMPurify: Cross-realm IN_PLACE sanitization leaves executable markup intact via realm-bound `instanceof` checks","id":"CVE-2026-49458","kev_date_added":null,"published":"2026-07-14"},{"cvss_score":6.1,"headline":"DOMPurify: IN_PLACE mode preserves attributes of a clobbered root element, allowing XSS via attacker-controlled root DOM","id":"CVE-2026-49459","kev_date_added":null,"published":"2026-07-14"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-16","vendors":["cure53"]},"summary":"DOMPurify fails to sanitize selectedcontent elements, allowing attackers to inject XSS payloads that execute in the victim's browser.","url":"https://insights.sbomify.com/CVE-2026-47423/"}