Skip to main content
No exploitation reportedFix available

CVE-2018-15531

No exploitation reported by the sources we read.

  • Published2018-09-26
  • Fixed in1.74.0
  • WeaknessCWE-611

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

JavaMelody before 1.74.0 has XXE via parseSoapMethodName in bull/javamelody/PayloadNameRequestWrapper.java.

Timeline

dates in UTC
  1. 2018-09-2622:29CVE publishedNVD
  2. 2026-10-2319:23EPSS crossed 10 %FIRST EPSS

Observed activity

isMalicious corpus · updated 2026-10-23 21:37 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2018-15531?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2018-15531?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD · OSV
Javamelody project javamelody
BranchAffectedFixed in
1.74< 1.74.01.74.0

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Fix

  1. Update Javamelody project javamelody to 1.74.0

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
none listed
PoC-in-GitHub

Sources

  • NVDCVSS 3.09.8read 2026-10-23
  • NVDCVSS 2.07.5read 2026-10-23
  • NVDweakness (CWE)CWE-611read 2026-10-23
  • FIRST EPSSEPSS score27.9 %read 2026-10-23
  • OSVaffected packages—

Technical details

CVSS v3 Vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Published
2018-09-26
Last Modified
2026-06-17
NVD status
Modified

Frequently asked questions

What is CVE-2018-15531?

JavaMelody before 1.74.0 has XXE via parseSoapMethodName in bull/javamelody/PayloadNameRequestWrapper.java.

Is CVE-2018-15531 actively exploited?

Active exploitation of CVE-2018-15531 has not been confirmed. Its EPSS score was 27.9% on 2026-10-23, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2018-15531?

CVE-2018-15531 has a CVSS v3 base score of 9.8 (CRITICAL severity), with vector string CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.

Hear about the next vulnerability in your software

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month