{"answers":{"affected":"2 open source packages ship an affected version, including sanitize-html. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-25225 exists.","fix":"Upgrade sanitize-html to 2.0.0-beta or later.","what":"CVE-2019-25225 is a medium-severity cross-site scripting vulnerability in apostrophecms:sanitize-html, published on 8 Sep 2025. 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-25225 and fix it if it is affected.\n\nWhat it is: CVE-2019-25225 is a medium-severity cross-site scripting vulnerability in apostrophecms:sanitize-html, published on 8 Sep 2025. 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-2019-25225 exists.\n\nAffected packages and fixed versions:\n- sanitize-html (npm): affected all versions; fixed in 2.0.0-beta\n- sanitize-html (npm): affected all versions; fixed in 2.0.0-beta\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-25225/ (Markdown: https://insights.sbomify.com/CVE-2019-25225/index.md)","id":"CVE-2019-25225","markdown":"https://insights.sbomify.com/CVE-2019-25225/index.md","name":"CVE-2019-25225","record":{"aliases":["CLSA-2026-1775003160","GHSA-qhxp-v273-g94h","ROOT-APP-NPM-CVE-2019-25225","UBUNTU-CVE-2019-25225"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"HTML sanitization library","requires_auth":"none","summary":"Attackers can execute arbitrary scripts via malicious input when using the custom transformTags option in the sanitize-html library.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Checkmarx","cpe":[{"product":"sanitize-html","vendor":"apostrophecms"}],"cvss":{"score":6.1,"severity":"medium","source":"cna","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":"`sanitize-html` prior to version 2.0.0-beta is vulnerable to Cross-site Scripting (XSS). The `sanitizeHtml()` function in `index.js` does not sanitize content when using the custom `transformTags` option, which is intended to convert attribute values into text. As a result, malicious input can be transformed into executable code.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"sanitize-html is vulnerable to XSS through incomprehensive sanitization","id":"CVE-2019-25225","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"xss","year":"2019"},"n_packages":2,"n_references":4,"next":{"headline":"Dongyoung Media DM-AP240T/W Unauthenticated Configuration Disclosure","id":"CVE-2019-25226"},"packages":[{"ecosystem":"npm","fixed":["2.0.0-beta"],"introduced":["0"],"last_affected":[],"package":"sanitize-html","purl":null,"source":"GHSA-qhxp-v273-g94h"},{"ecosystem":"npm","fixed":["2.0.0-beta"],"introduced":["0"],"last_affected":[],"package":"sanitize-html","purl":"pkg:npm/sanitize-html","source":"GHSA-qhxp-v273-g94h"}],"prev":{"headline":"WP Database Backup \u003c 5.2 - Unauthenticated OS Command Injection","id":"CVE-2019-25224"},"products":["apostrophecms:sanitize-html"],"published":"2025-09-08","related":[{"cvss_score":6.1,"headline":"Cross-site scripting in apostrophecms:sanitize-html","id":"CVE-2014-125128","kev_date_added":null,"published":"2025-09-08"},{"cvss_score":6.1,"headline":"Cross-Site Scripting in sanitize-html","id":"CVE-2016-1000237","kev_date_added":null,"published":"2020-01-23"},{"cvss_score":5.3,"headline":"sanitize-html Information Exposure vulnerability","id":"CVE-2024-21501","kev_date_added":null,"published":"2024-02-24"},{"cvss_score":5.3,"headline":"Regular Expression Denial of Service (ReDoS)","id":"CVE-2022-25887","kev_date_added":null,"published":"2022-08-30"},{"cvss_score":5.3,"headline":"Improper Input Validation in sanitize-html","id":"CVE-2021-26539","kev_date_added":null,"published":"2021-02-08"},{"cvss_score":5.3,"headline":"Improper Input Validation in sanitize-html","id":"CVE-2021-26540","kev_date_added":null,"published":"2021-02-08"}],"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":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-09-08","vendors":["apostrophecms"]},"summary":"Attackers can execute arbitrary scripts via malicious input when using the custom transformTags option in the sanitize-html library.","url":"https://insights.sbomify.com/CVE-2019-25225/"}