CVE-2025-36049
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIBM webMethods Integration Server 10.5, 10.7, 10.11, and 10.15 is vulnerable to an XML external entity injection (XXE) attack when processing XML data. A remote authenticated attacker could exploit this vulnerability to execute arbitrary commands.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceIBM webMethods Integration Server versions 10.5, 10.7, 10.11, and 10.15 is vulnerable to XML External Entity (XXE) injection when processing XML data. A remote authenticated attacker can exploit this vulnerability by submitting malicious XML containing external entity references to execute arbitrary commands or read sensitive files from the server.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 10.5= 10.7= 10.11= 10.15CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Integration Server versionLocate the Integration Server installation directory and check the version file or banner, typically found in the product's versioninfo or about section of the Admin UIAffected if The installed version is 10.5, 10.7, 10.11, or 10.15 exactly as listed in affected versions
-
Locate XML parser configurationAccess Integration Server Administrator UI or navigate to the XML parser configuration files in the IS directory structure, typically under config or XMLServices folderAffected if XML parser configuration files exist and external entity processing settings are present
-
Check XML external entity settingsInspect the XML parser configuration for settings related to 'external entity', 'DOCTYPE', 'XXE', or 'entity resolution'. Look for boolean flags that enable or disable external entity processing.Affected if External entity processing is explicitly enabled or set to allow DOCTYPE declarations with external references
-
Verify XML processing endpoint availabilityIdentify any services, endpoints, or APIs that accept XML input. Check which services invoke the XML parser to process incoming XML documents.Affected if There are active XML processing endpoints that accept untrusted XML input from authenticated users
-
Audit parser security configurationReview Integration Server XML parser security settings in the Administrator console under XML or parser settings. Check for absence of strict input validation that rejects DOCTYPE declarations.Affected if No strict input validation is configured and the parser allows DOCTYPE declarations with external entity references
A user is affected if they run IBM webMethods Integration Server versions 10.5, 10.7, 10.11, or 10.15 AND have XML external entity processing enabled in their parser configuration, especially if the server accepts XML input from authenticated users.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataDisable XML external entity processing in the Integration Server's XML parser configuration or implement strict input validation to reject XML containing DOCTYPE declarations with external entity references.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-36049 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-36049 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data