{"answers":{"affected":"2 open source packages ship an affected version, including @jitbit/htmlsanitizer.","exploited":"There is no known exploitation of CVE-2025-29771 in the wild and no public exploit code.","fix":"Upgrade @jitbit/htmlsanitizer to 2.0.3 or later.","what":"CVE-2025-29771 is a medium-severity cross-site scripting vulnerability in jitbit HtmlSanitizer, published on 14 Mar 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-2025-29771 and fix it if it is affected.\n\nWhat it is: CVE-2025-29771 is a medium-severity cross-site scripting vulnerability in jitbit HtmlSanitizer, published on 14 Mar 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: There is no known exploitation of CVE-2025-29771 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- @jitbit/htmlsanitizer (npm): affected all versions; fixed in 2.0.3\n- @jitbit/htmlsanitizer (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-2025-29771/ (Markdown: https://insights.sbomify.com/CVE-2025-29771/index.md)","id":"CVE-2025-29771","markdown":"https://insights.sbomify.com/CVE-2025-29771/index.md","name":"CVE-2025-29771","record":{"aliases":["GHSA-vhv4-fh94-jm5x"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"JavaScript HTML sanitizer","requires_auth":"none","summary":"Attackers can execute arbitrary scripts via XSS when HtmlSanitizer is used with contentEditable elements due to post-sanitization beautification flaws.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N","version":"4.0"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"HtmlSanitizer is a client-side HTML Sanitizer. Versions prior to 2.0.3 have a cross-site scripting vulnerability when the sanitizer is used with a `contentEditable` element to set the elements `innerHTML` to a sanitized string produced by the package. If the code is particularly crafted to abuse the code beautifier, that runs AFTER sanitation. The issue is patched in version 2.0.3.","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":"HtmlSanitizer vulnerable to XSS when used with contentEditable","id":"CVE-2025-29771","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"xss","year":"2025"},"n_packages":2,"n_references":2,"next":{"headline":"OpenEMR allows Reflected XSS in CAMOS new.php","id":"CVE-2025-29772"},"packages":[{"ecosystem":"npm","fixed":["2.0.3"],"introduced":["0"],"last_affected":[],"package":"@jitbit/htmlsanitizer","purl":null,"source":"GHSA-vhv4-fh94-jm5x"},{"ecosystem":"npm","fixed":["2.0.3"],"introduced":["0"],"last_affected":[],"package":"@jitbit/htmlsanitizer","purl":"pkg:npm/%40jitbit/htmlsanitizer","source":"GHSA-vhv4-fh94-jm5x"}],"prev":{"headline":"vLLM denial of service via outlines unbounded cache on disk","id":"CVE-2025-29770"},"products":["HtmlSanitizer"],"published":"2025-03-14","related":[],"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":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-03-18","vendors":["jitbit"]},"summary":"Attackers can execute arbitrary scripts via XSS when HtmlSanitizer is used with contentEditable elements due to post-sanitization beautification flaws.","url":"https://insights.sbomify.com/CVE-2025-29771/"}