CVE-2016-1000273 is a critical-severity (CVSS 10) vulnerability in net.bull.javamelody:javamelody-core. A fix is available for net.bull.javamelody:javamelody-core — see the affected versions and patch details below.
Java Melody vulnerable to cross-site scripting
Real-World Exposure
net.bull.javamelody:javamelody-coreReal-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 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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | net.bull.javamelody:javamelody-core | all versions | 1.61.0net.bull.javamelody:javamelody-core:1.61.0 |
Detection & mitigation playbook
Open-source dependencyDetect
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-2016-1000273 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
Is CVE-2016-1000273 in your dependencies?
Find it across Maven, including transitive dependencies.