{"answers":{"affected":"2 open source packages ship an affected version, including dompurify. It affects 2 products.","exploited":"There is no known exploitation of CVE-2019-16728 in the wild and no public exploit code.","fix":"Upgrade dompurify to 2.0.3 or later.","what":"CVE-2019-16728 is a medium-severity cross-site scripting vulnerability in Debian Debian Linux, published on 24 Sep 2019. 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-2019-16728 and fix it if it is affected.\n\nWhat it is: CVE-2019-16728 is a medium-severity cross-site scripting vulnerability in Debian Debian Linux, published on 24 Sep 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2019-16728 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- dompurify (npm): affected all versions; fixed in 2.0.3\n- dompurify (npm): affected all versions; fixed in 2.0.3\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-2019-16728/ (Markdown: https://insights.sbomify.com/CVE-2019-16728/index.md)","id":"CVE-2019-16728","markdown":"https://insights.sbomify.com/CVE-2019-16728/index.md","name":"CVE-2019-16728","record":{"aliases":["GHSA-chqj-j4fh-rw7m","UBUNTU-CVE-2019-16728"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"JavaScript sanitization library","requires_auth":"none","summary":"An attacker can execute arbitrary JavaScript via mutation XSS in DOMPurify when sanitizing SVG or MATH elements.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"dompurify","vendor":"cure53"},{"product":"debian_linux","vendor":"debian"}],"cvss":{"score":6.1,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"DOMPurify before 2.0.1 allows XSS because of innerHTML mutation XSS (mXSS) for an SVG element or a MATH element, as demonstrated by Chrome and Safari.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Cross-Site Scripting in dompurify","id":"CVE-2019-16728","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":"debian:debian_linux","products":["debian:debian_linux"],"type":"xss","year":"2019"},"n_packages":2,"n_references":2,"next":{"headline":"Privilege escalation in n/a","id":"CVE-2019-16729"},"packages":[{"ecosystem":"npm","fixed":["2.0.3"],"introduced":["0"],"last_affected":[],"package":"dompurify","purl":null,"source":"GHSA-chqj-j4fh-rw7m"},{"ecosystem":"npm","fixed":["2.0.3"],"introduced":["0"],"last_affected":[],"package":"dompurify","purl":"pkg:npm/dompurify","source":"GHSA-chqj-j4fh-rw7m"}],"prev":{"headline":"Joomla! XSS in Default Templates","id":"CVE-2019-16725"},"products":["n/a"],"published":"2019-09-24","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":8.2,"headline":"DOMPurify XSS via `selectedcontent` re-clone","id":"CVE-2026-47423","kev_date_added":null,"published":"2026-07-14"},{"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)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"An attacker can execute arbitrary JavaScript via mutation XSS in DOMPurify when sanitizing SVG or MATH elements.","url":"https://insights.sbomify.com/CVE-2019-16728/"}