dbcve.org
Webmethods IntegrationApplication · Ibm

CVE-2025-36048

HIGH · 7.2 CVSS v3.1 Published 2025-06-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

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 · unedited
IBM webMethods Integration Server 10.5, 10.7, 10.11, and 10.15 could allow a privileged user to escalate their privileges when handling external entities due to execution with unnecessary privileges.

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 · moderate confidence

IBM webMethods Integration Server versions 10.5, 10.7, 10.11, and 10.15 contains a privilege escalation vulnerability where handling external entities (likely XML-based) executes with unnecessary privileges. An authenticated privileged user can exploit this to gain higher-level administrative or system-level access.

MitigationApply IBM's vendor patch for this vulnerability and audit configurations related to external entity processing to ensure least-privilege execution principles.

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
Webmethods IntegrationApplication
Affected:= 10.5= 10.7= 10.11= 10.15

CVSS 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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify IBM webMethods Integration Server installation and version
    Locate the Integration Server installation directory. Check for version info in product files, typically found in a version.properties file, about dialog, or installer records under the installation root directory.
    Affected if The installed version matches 10.5, 10.7, 10.11, or 10.15 exactly.
  2. Confirm the exact version number
    Open the version file or use the product's built-in version command if available. Record the full version string including any patch levels.
    Affected if The version string begins with 10.5, 10.7, 10.11, or 10.15.
  3. Locate XML processing configuration
    Search for XML parser or document handler configuration files within the Integration Server directory, typically under /config, /parser, or /xml subdirectories. Look for settings related to XML parsing, document transformation, or external entity handling.
    Affected if XML parser configuration allows or does not disable external entity resolution.
  4. Check for external entity processing enablement
    Inspect the XML parser settings for keywords such as 'external-entities', 'DTD processing', 'allow外部实体', or similar settings that control XXE behavior. Also check if the Integration Server has any custom XML handlers deployed.
    Affected if External entity processing or DTD processing is explicitly enabled or left at default in the parser configuration.
  5. Verify Integration Server runs with elevated privileges
    Check the service or process account under which the Integration Server runs. On Windows, view the service properties. On Unix/Linux, check the process owner or startup scripts.
    Affected if The Integration Server runs under an administrator, root, or service account with higher privileges than standard user accounts.

Your environment is affected if IBM webMethods Integration Server version 10.5, 10.7, 10.11, or 10.15 is installed AND XML external entity processing is enabled, allowing an authenticated privileged user to potentially escalate to administrative or system-level access.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply IBM's vendor patch for this vulnerability and audit configurations related to external entity processing to ensure least-privilege execution principles.

Fix this in Webmethods Integration Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-36048 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-36048 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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