How severe is CVE-2013-6235?

No CVSS score has been assigned to CVE-2013-6235 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2013-6235?

CVE-2013-6235 affects the following packages: com.jamonapi:jamon (Maven). Ecosystems affected: Maven.

How do I fix CVE-2013-6235?

Update com.jamonapi:jamon to 2.80 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-6235 is resolved across your whole dependency graph.

How do I detect CVE-2013-6235 in my Maven dependencies?

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

How do I mitigate CVE-2013-6235 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-2013-6235 actively exploited in the wild?

Yes. There are 2 known exploit references for CVE-2013-6235, including 2 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2013-6235?

CVE-2013-6235 has an EPSS (Exploit Prediction Scoring System) score of 2.2%, placing it in the 83th 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-2013-6235?

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

CVE-2013-6235 was published on May 14, 2022 and was last updated on December 5, 2024. 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

CVE-2013-6235 — jamon

CVE-2013-6235 is a Cross-site Scripting (XSS) vulnerability in com.jamonapi:jamon. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for com.jamonapi:jamon — see the affected versions and patch details below.

Improper Neutralization of Input During Web Page Generation in JAMon

Published

May 14, 2022

Updated

Dec 5, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

2 known

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

EPSS Exploitation Probability

via FIRST.org ↗

2.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs83th percentile — riskier than 83% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

☕com.jamonapi:jamon

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

Multiple cross-site scripting (XSS) vulnerabilities in JAMon (Java Application Monitor) 2.7 and earlier allow remote attackers to inject arbitrary web script or HTML via the (1) listenertype or (2) currentlistener parameter to mondetail.jsp or ArraySQL parameter to (3) mondetail.jsp, (4) jamonadmin.jsp, (5) sql.jsp, or (6) exceptions.jsp.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.jamonapi:jamon`	all versions	2.80`com.jamonapi:jamon:2.80`

Affected Products

1 product · 10 configurations

Application

java application monitorsteve_souza

≤ 2.7

9 versions

1.01.012.02.12.22.32.42.52.6

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Multiple cross-site scripting (XSS) vulnerabilities in JAMon (Java Appli…

packetstormsecurity.comNVDOct 2018

Report on seclists.org

seclists.orgNVDOct 2018

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.jamonapi:jamon, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.jamonapi:jamon to 2.80 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-6235 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-2013-6235 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works