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

Advisory record · `GHSA-pcm9-fp55-563v`

- **Identifiers:** `GHSA-pcm9-fp55-563v` · `CVE-2011-4457`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **Weakness (CWE):** [CWE-200](https://cwe.mitre.org/data/definitions/200.html)
- **Tags:** [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.md)
- **Published:** 17 May 2022
- **Updated:** 2 Dec 2024
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 17 May 2022, 05:36 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `com.googlecode.owasp-java-html-sanitizer:owasp-java-html-sanitizer` (Maven): affected `<88`; fixed in `88`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The owasp-java-html-sanitizer package before version 88 is affected when JavaScript is disabled. A user-assisted remote attacker can use a crafted FORM element inside a NOSCRIPT element to obtain potentially sensitive information; the title describes a redirect to an arbitrary URL, but the source gives few details. Upgrade to version 88.

Written 8 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.014, the 72nd percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:12 UTC: First seen by agentprime
- 31 Oct 2026, 15:12 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-pcm9-fp55-563v)

## Sources

- [GitHub Advisory Database: GHSA-pcm9-fp55-563v](https://github.com/advisories/GHSA-pcm9-fp55-563v)
- [OSV: GHSA-pcm9-fp55-563v](https://osv.dev/vulnerability/GHSA-pcm9-fp55-563v)
- <https://nvd.nist.gov/vuln/detail/CVE-2011-4457>
- <https://github.com/OWASP/java-html-sanitizer/commit/2027d3df73f62eb30b7f08269f346989f03144bd>
- <https://github.com/OWASP/java-html-sanitizer>
- <https://github.com/OWASP/java-html-sanitizer/blob/35c506cfd452dba634202f13a7cc2e2a63ad7ee0/change_log.md?plain=1#L103>
- <https://github.com/OWASP/java-html-sanitizer/blob/35c506cfd452dba634202f13a7cc2e2a63ad7ee0/docs/cve20114457.md>
- <http://code.google.com/p/owasp-java-html-sanitizer/wiki/CVE20114457>
- <http://owasp-java-html-sanitizer.googlecode.com/svn/trunk/CHANGE_LOG.html>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-pcm9-fp55-563v>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-pcm9-fp55-563v/>. Everything for agents: <https://agentprime.io/llms.txt>.
