How severe is CVE-2018-12432?

CVE-2018-12432 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-2018-12432?

CVE-2018-12432 affects the following packages: net.bull.javamelody:javamelody-core (Maven). Ecosystems affected: Maven.

How do I fix CVE-2018-12432?

Update net.bull.javamelody:javamelody-core to 1.61.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-12432 is resolved across your whole dependency graph.

How do I detect CVE-2018-12432 in my Maven dependencies?

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

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

Yes. There are 1 known exploit references for CVE-2018-12432, including 1 in-the-wild exploitation 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-2018-12432?

CVE-2018-12432 has an EPSS (Exploit Prediction Scoring System) score of 0.7%, placing it in the 53th 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-2018-12432?

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

CVE-2018-12432 was published on June 14, 2018 and was last updated on October 24, 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-2018-12432 — javamelody-core

MEDIUMFix: javamelody/javamelody@e0497c1

CVE-2018-12432 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in net.bull.javamelody:javamelody-core. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for net.bull.javamelody:javamelody-core — see the affected versions and patch details below.

Cross-site Scripting in JavaMelody

Also known asGHSA-g66q-grxc-64j3

Published

Jun 14, 2018

Updated

Oct 24, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

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

EPSS Exploitation Probability

via FIRST.org ↗

0.7%probability of exploitation in next 30 days

Lower Risk0.00%

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

☕net.bull.javamelody:javamelody-core

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

JavaMelody through 1.60.0 has XSS via the counter parameter in a clear_counter action to the /monitoring URI.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`net.bull.javamelody:javamelody-core`	all versions	1.61.0`net.bull.javamelody:javamelody-core:1.61.0`

Affected Products

1 product · 1 configurations

Application

javamelodyjavamelody_project

≤ 1.60.0

range

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.

JavaMelody through 1.60.0 has XSS via the counter parameter in a clear_c…

github.comNVDAug 2018

Detection & mitigation playbook

Open-source dependency

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

JavaMelody through 1.60.0 has XSS via the counter parameter in a clear_counter action to the /monitoring URI.

O3 Security · Impact-Aware SCA

Is CVE-2018-12432 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 or Metasploit module yet. 1 public proof-of-concept reference is listed on this page.

Timeline

Disclosed

Jun 14, 2018

First exploit

Aug 2, 2018

Last updated

Oct 24, 2026

Identifiers

CVE-2018-12432

GHSA-g66q-grxc-64j3

References

Advisorynvd.nist.gov · CVE 2018 12432 Webgithub.com · e0497c1980acebd257d3da78dfde29ae9bdffdf6 Evidencegithub.com · Attack Vector JavaMelody

Related vulnerabilities

Also affects javamelody-core

This CVE is medium severity; 3 of 3 other CVEs affecting javamelody-core are rated as high or higher (top: critical).

CVE-2016-1000273CVE-2013-4378CVE-2018-15531

Same weakness: CWE-79

This CVE is medium severity; 5 of 5 other CVEs with CWE-79 are rated as high or higher (top: critical).

CVE-2026-55649CVE-2026-113787CVE-2026-44267CVE-2026-96632CVE-2026-9086Browse all CWE-79

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 24, 2026