How severe is CVE-2016-10006?

CVE-2016-10006 has a CVSS score of 6.1/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2016-10006?

CVE-2016-10006 affects the following packages: org.owasp.antisamy:antisamy (Maven). Ecosystems affected: Maven.

How do I fix CVE-2016-10006?

Update org.owasp.antisamy:antisamy to 1.5.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2016-10006 is resolved across your whole dependency graph.

How do I detect CVE-2016-10006 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.owasp.antisamy:antisamy, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

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

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is CVE-2016-10006 actively exploited in the wild?

No public exploit code has been indexed for CVE-2016-10006 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-2016-10006?

CVE-2016-10006 has an EPSS (Exploit Prediction Scoring System) score of 2.4%, placing it in the 84th 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-2016-10006?

CVE-2016-10006 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2016-10006 published, and has it been updated?

CVE-2016-10006 was published on December 24, 2016 and was last updated on March 15, 2026. 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

MEDIUM severity

CVE-2016-10006 — antisamy

MEDIUM

CVE-2016-10006 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in org.owasp.antisamy:antisamy. A fix is available for org.owasp.antisamy:antisamy — see the affected versions and patch details below.

OWASP AntiSamy vulnerable to Cross-site Scripting

Also known asGHSA-683w-6h9j-57wq

Published

Dec 24, 2016

Updated

Mar 15, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

2.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs84th percentile — riskier than 84% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

☕org.owasp.antisamy:antisamy

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

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.owasp.antisamy:antisamy`	all versions	1.5.5`org.owasp.antisamy:antisamy:1.5.5`

Affected Products

1 product · 1 configurations

Application

antisamyantisamy_project

< 1.5.5

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.owasp.antisamy:antisamy, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.owasp.antisamy:antisamy to 1.5.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2016-10006 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2016-10006 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

6.1/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Raw vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

CWE Classification

CWE-79Cross-site Scripting (XSS)

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

Timeline

Disclosed

Dec 24, 2016

Last updated

Mar 15, 2026

Identifiers

CVE-2016-10006

GHSA-683w-6h9j-57wq

References

Advisorysecuritytracker.com Advisorysecurityfocus.com Advisorynvd.nist.gov · CVE 2016 10006 Fixgithub.com Webweb.archive.org Webweb.archive.org Packagegithub.com · antisamy

Related vulnerabilities

Also affects antisamy

This CVE is medium severity, in line with the other 6 CVEs affecting antisamy.

CVE-2024-23635CVE-2023-43643CVE-2022-28367CVE-2022-29577CVE-2021-35043CVE-2017-14735

Same weakness: CWE-79

This CVE is medium severity; 1 of 2 other CVEs with CWE-79 is rated as high or higher (top: moderate).

CVE-2026-126075CVE-2026-126063Browse all CWE-79

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedMar 15, 2026