Skip to content
Fencer Intel
medium 6.1

CVE-2016-10006 json

OWASP AntiSamy vulnerable to Cross-site Scripting

published 9y ago modified 4mo ago also GHSA-683w-6h9j-57wq , EUVD-2018-0515

cvss
6.1
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.4%
EPSS 2.4% chance of exploitation in 30 days, percentile 83%
public exploits
0
none known

Summary

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.

Patch / fix

  • maven org.owasp.antisamy:antisamy 1.5.5
  • antisamy_project antisamy 1.5.5
  • libowasp-antisamy-java Debian 14, Debian 13 1.7.4-1

debian advisories DEBIAN-CVE-2016-10006

Is CVE-2016-10006 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

2.35% chance of exploitation in the next 30 days, higher than 83% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 6.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:P/A:N
GitHub 3.1 6.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Affected packages

ecosystem package affected fixed in
maven org.owasp.antisamy:antisamy
<1.5.5
1.5.5

Classification

Weakness
  • CWE-79 Improper Neutralization of Input During Web Page Generation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.