How severe is CVE-2011-4457?

No CVSS score has been assigned to CVE-2011-4457 yet. Review the advisory details and affected package list to assess your exposure.

How do I fix CVE-2011-4457?

Update com.googlecode.owasp-java-html-sanitizer:owasp-java-html-sanitizer to 88 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2011-4457 is resolved across your whole dependency graph.

How do I mitigate CVE-2011-4457 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2011-4457?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2011-4457 can be triaged on real exposure rather than presence alone.

Is CVE-2011-4457 actively exploited in the wild?

No public exploit code has been indexed for CVE-2011-4457 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2011-4457?

CVE-2011-4457 has an EPSS (Exploit Prediction Scoring System) score of 1.4%, placing it in the 71th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2011-4457?

CVE-2011-4457 is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2011-4457 published, and has it been updated?

CVE-2011-4457 was published on May 17, 2022 and was last updated on December 2, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

CVE-2011-4457 — owasp-java-html-sanitizer

Fix: OWASP/java-html-sanitizer@2027d3d

CVE-2011-4457 is a Information Exposure vulnerability in com.googlecode.owasp-java-html-sanitizer:owasp-java-html-sanitizer. A fix is available for com.googlecode.owasp-java-html-sanitizer:owasp-java-html-sanitizer — see the affected versions and patch details below.

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

Published

May 17, 2022

Updated

Dec 2, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 18, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs71th percentile — riskier than 71% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

1 pkg affected

☕com.googlecode.owasp-java-html-sanitizer:owasp-java-html-sanitizer

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.googlecode.owasp-java-html-sanitizer:owasp-java-html-sanitizer`	all versions	88`com.googlecode.owasp-java-html-sanitizer:owasp-java-html-sanitizer:88`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.googlecode.owasp-java-html-sanitizer:owasp-java-html-sanitizer, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.googlecode.owasp-java-html-sanitizer:owasp-java-html-sanitizer to 88 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2011-4457 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2011-4457 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2011-4457. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2011-4457 in your dependencies?

O3 Security finds CVE-2011-4457 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works