Java Melody vulnerable to cross-site scripting

published 2022-07-20 4y ago modified 2026-09-10 last mo. also GHSA-cqhr-jqvc-qw9p

cvss: 10.0; version 3.1, GitHub
cisa kev: Not listed; not in CISA's catalog
epss: —; no EPSS score yet
public exploits: 0; none known

JavaMelody is a monitoring tool for JavaEE applications. Versions prior to 1.61.0 are vulnerable to a cross-site scripting (XSS) attack. This issue was patched in version 1.61.0, and users are recommended to upgrade to the latest version. There are no known workarounds.

Patch / fix

fixed in 1 links 1

maven net.bull.javamelody:javamelody-core 1.61.0

github.com/javamelody/javamelody@e0497c1 commit

Is CVE-2016-1000273 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

CVSS scores

assigned by	version	score	vector
GitHub	3.1	10.0	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Affected packages

ecosystem	package	affected	fixed in
maven	net.bull.javamelody:javamelody-core	<1.61.0	1.61.0

Classification

Weakness

CWE-79 Improper Neutralization of Input During Web Page Generation

References

Sources

GitHub Advisory GHSA-cqhr-jqvc-qw9p

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.