Is there a fix for CVE-2011-4457?

Yes. CVE-2011-4457 is fixed in 88. Upgrade to this version or later.

Is CVE-2011-4457 exploitable, and should I be worried?

Whether CVE-2011-4457 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-2011-4457 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.

CVE-2011-4457

Q: What is CVE-2011-4457?

CVE-2011-4457 is a low-severity security vulnerability in com.googlecode.owasp-java-html-sanitizer:owasp-java-html-sanitizer (maven), affecting versions < 88. It is fixed in 88.

Q: How do I fix CVE-2011-4457?

Upgrade com.googlecode.owasp-java-html-sanitizer:owasp-java-html-sanitizer to 88 or later.

Summary

OWASP HTML Sanitizer allows redirecting to an arbitrary URL when JavaScript is disabled

OWASP HTML Sanitizer (aka owasp-java-html-sanitizer) before 88, when JavaScript is disabled, allows user-assisted remote attackers to obtain potentially sensitive information via a crafted FORM element within a NOSCRIPT element.

Impact

Affected versions

com.googlecode.owasp-java-html-sanitizer:owasp-java-html-sanitizer (< 88)

Security releases

com.googlecode.owasp-java-html-sanitizer:owasp-java-html-sanitizer → 88 (maven)

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

Upgrade com.googlecode.owasp-java-html-sanitizer:owasp-java-html-sanitizer to 88 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2011-4457? CVE-2011-4457 is a low-severity security vulnerability in com.googlecode.owasp-java-html-sanitizer:owasp-java-html-sanitizer (maven), affecting versions < 88. It is fixed in 88.
Which versions of com.googlecode.owasp-java-html-sanitizer:owasp-java-html-sanitizer are affected by CVE-2011-4457? com.googlecode.owasp-java-html-sanitizer:owasp-java-html-sanitizer (maven) versions < 88 is affected.
Is there a fix for CVE-2011-4457? Yes. CVE-2011-4457 is fixed in 88. Upgrade to this version or later.
Is CVE-2011-4457 exploitable, and should I be worried? Whether CVE-2011-4457 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-2011-4457 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-2011-4457? Upgrade com.googlecode.owasp-java-html-sanitizer:owasp-java-html-sanitizer to 88 or later.

Other vulnerabilities in com.googlecode.owasp-java-html-sanitizer:owasp-java-html-sanitizer

CVE-IDSeverityPackage summary

CVE-2025-66021Highcom.googlecode.owasp-java-html-sanitizer:owasp-java-html-sanitizer: OWASP Java HTML Sanitizer is vulnerable to XSS via noscript tag and improper style tag sanitization CVE-2021-42575Criticalcom.googlecode.owasp-java-html-sanitizer:owasp-java-html-sanitizer: Policies not properly enforced in OWASP Java HTML Sanitizer