CVE-2018-15531
CVE-2018-15531 is a critical-severity vulnerability in Javamelody Project Javamelody with a CVSS 3.x base score of 9.8. Its EPSS exploit-prediction score of 28% places it in the 98th percentile, indicating an elevated likelihood of exploitation. The underlying weakness is classified as CWE-611.
Key facts
- Severity: Critical (CVSS 3.x base score 9.8)
- CVSS v2: 7.5
- EPSS exploit prediction: 28% (98th percentile)
- Actively exploited: Not listed in CISA KEV
- Weakness: CWE-611
- Affected product: Javamelody Project Javamelody
- Published:
- Last modified:
Description
JavaMelody before 1.74.0 has XXE via parseSoapMethodName in bull/javamelody/PayloadNameRequestWrapper.java.
Frequently asked questions
- What is CVE-2018-15531?
- JavaMelody before 1.74.0 has XXE via parseSoapMethodName in bull/javamelody/PayloadNameRequestWrapper.java.
- How severe is CVE-2018-15531?
- CVE-2018-15531 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
- Is CVE-2018-15531 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 28% (98th percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2018-15531?
- CVE-2018-15531 affects Javamelody Project Javamelody. See the affected-products list for the exact vulnerable versions.
- How do I fix CVE-2018-15531?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
- When was CVE-2018-15531 published?
- CVE-2018-15531 was published on 2018-09-26 and last updated on 2026-06-17.
References
- http://www.openwall.com/lists/oss-security/2018/09/25/3
- https://github.com/javamelody/javamelody/commit/ef111822562d0b9365bd3e671a75b65bd0613353
- https://github.com/javamelody/javamelody/wiki/ReleaseNotes
- https://jenkins.io/security/advisory/2018-09-25/
Affected products (1)
- cpe:2.3:a:javamelody_project:javamelody:*:*:*:*:*:*:*:*
More vulnerabilities in Javamelody Project Javamelody
- CVE-2018-12432 — Medium (CVSS 6.1): JavaMelody through 1.60.0 has XSS via the counter parameter in a clear_counter action to the /monitoring URI.
All CVEs affecting Javamelody Project Javamelody →
Other CWE-611 (Improper Restriction of XML External Entity Reference (XXE)) vulnerabilities
- CVE-2022-22486 — Critical (CVSS 10.0): IBM Tivoli Workload Scheduler 9.4, 9.5, and 10.1 is vulnerable to an XML External Entity Injection (XXE) attack when…
- CVE-2019-14678 — Critical (CVSS 10.0): SAS XML Mapper 9.45 has an XML External Entity (XXE) vulnerability that can be leveraged by malicious attackers in…
- CVE-2015-9280 — Critical (CVSS 10.0): MailEnable before 8.60 allows XXE via an XML document in the request.aspx Options parameter.
- CVE-2018-1000838 — Critical (CVSS 10.0): autopsy version <= 4.9.0 contains a XML External Entity (XXE) vulnerability in CaseMetadata XML Parser that can result…
- CVE-2018-1000837 — Critical (CVSS 10.0): UML Designer version <= 8.0.0 contains a XML External Entity (XXE) vulnerability in XML parser for plugins that can…
- CVE-2018-1000835 — Critical (CVSS 10.0): KeePassDX version <= 2.5.0.0beta17 contains a XML External Entity (XXE) vulnerability in kdbx file parser that can…
Browse all CWE-611 (Improper Restriction of XML External Entity Reference (XXE)) vulnerabilities →