What is CVE-2025-29771?

CVE-2025-29771 is a medium-severity cross-site scripting (XSS) vulnerability in @jitbit/htmlsanitizer (npm), affecting versions < 2.0.3. It is fixed in 2.0.3. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.

Which versions of @jitbit/htmlsanitizer are affected by CVE-2025-29771?

@jitbit/htmlsanitizer (npm) versions < 2.0.3 is affected.

Is there a fix for CVE-2025-29771?

Yes. CVE-2025-29771 is fixed in 2.0.3. Upgrade to this version or later.

Is CVE-2025-29771 exploitable, and should I be worried?

Whether CVE-2025-29771 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2025-29771 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2025-29771?

Upgrade @jitbit/htmlsanitizer to 2.0.3 or later.

CVE-2025-29771 in @jitbit/htmlsanitizer

Q: Which versions of @jitbit/htmlsanitizer are affected by CVE-2025-29771?

@jitbit/htmlsanitizer (npm) versions < 2.0.3 is affected.

Q: Is there a fix for CVE-2025-29771?

Yes. CVE-2025-29771 is fixed in 2.0.3. Upgrade to this version or later.

Q: Is CVE-2025-29771 exploitable, and should I be worried?

Whether CVE-2025-29771 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2025-29771 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2025-29771?

Upgrade @jitbit/htmlsanitizer to 2.0.3 or later.

CVE-2025-29771

CVE-2025-29771 is a medium-severity cross-site scripting (XSS) vulnerability in @jitbit/htmlsanitizer (npm), affecting versions < 2.0.3. It is fixed in 2.0.3.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

JS Html Sanitizer allows XSS when used with contentEditable

Impact

XSS 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.

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

Affected versions

@jitbit/htmlsanitizer (< 2.0.3)

Security releases

@jitbit/htmlsanitizer → 2.0.3 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Patched in version 2.0.3

Frequently Asked Questions

What is CVE-2025-29771? CVE-2025-29771 is a medium-severity cross-site scripting (XSS) vulnerability in @jitbit/htmlsanitizer (npm), affecting versions < 2.0.3. It is fixed in 2.0.3. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
Which versions of @jitbit/htmlsanitizer are affected by CVE-2025-29771? @jitbit/htmlsanitizer (npm) versions < 2.0.3 is affected.
Is there a fix for CVE-2025-29771? Yes. CVE-2025-29771 is fixed in 2.0.3. Upgrade to this version or later.
Is CVE-2025-29771 exploitable, and should I be worried? Whether CVE-2025-29771 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2025-29771 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2025-29771? Upgrade @jitbit/htmlsanitizer to 2.0.3 or later.