How severe is CVE-2017-14735?

CVE-2017-14735 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-2017-14735?

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

How do I fix CVE-2017-14735?

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

How do I detect CVE-2017-14735 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-2017-14735 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-2017-14735 actively exploited in the wild?

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

CVE-2017-14735 has an EPSS (Exploit Prediction Scoring System) score of 1.7%, placing it in the 77th 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-2017-14735?

CVE-2017-14735 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-2017-14735 published, and has it been updated?

CVE-2017-14735 was published on September 25, 2017 and was last updated on October 20, 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-2017-14735 — antisamy

MEDIUM

CVE-2017-14735 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 Cross-site Scripting vulnerability

Also known asGHSA-q44v-xc3g-v7jq

Published

Sep 25, 2017

Updated

Oct 20, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

1.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs77th percentile — riskier than 77% 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

OWASP AntiSamy before 1.5.7 allows XSS via HTML5 entities, as demonstrated by use of : to construct a javascript: URL.

Affected Packages

1 total 1 fixed

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

Affected Products

1 product · 1 configurations

Application

antisamyantisamy_project

< 1.5.7

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.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-14735 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

OWASP AntiSamy before 1.5.7 allows XSS via HTML5 entities, as demonstrated by use of &colon; to construct a javascript: URL.

O3 Security · Impact-Aware SCA

Is CVE-2017-14735 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.0/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

Sep 25, 2017

Last updated

Oct 20, 2026

Identifiers

CVE-2017-14735

GHSA-q44v-xc3g-v7jq

References

Advisoryoracle.com · cpuoct2018 4428296 Advisoryoracle.com · cpujan2019 5072801 Advisoryoracle.com · cpujul2019 5072835 Advisorynvd.nist.gov · CVE 2017 14735 Advisorygithub.com · GHSA q44v xc3g v7jq Reportgithub.com Websecurityfocus.com Weboracle.com · cpujul2021 Weboracle.com · cpuApr2021 Weboracle.com · cpuapr2020 Weboracle.com · cpujan2020 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-2016-10006

Same weakness: CWE-79

This CVE is medium severity, in line with the other 2 CVEs with CWE-79.

CVE-2026-55649CVE-2026-113787Browse all CWE-79

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 20, 2026