dbcve.org
Webmethods Integration ServerApplication · Ibm

CVE-2025-14290

MEDIUM · 5.4 CVSS v3.1 Published 2026-05-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
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 (on prem) -Integration Server 10.15 through IS_10.15_Core_Fix2611.1 to IS_11.1_Core_Fix10 IBM webMethods Integration is vulnerable to server-side request forgery (SSRF). This may allow an authenticated attacker to send unauthorized requests from the system, potentially leading to network enumeration or facilitating other attacks.

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.15 through 11.1 contain a server-side request forgery (SSRF) vulnerability. An authenticated attacker can send unauthorized server-side requests from the affected system, enabling network enumeration and potentially facilitating attacks against internal infrastructure.

MitigationApply the appropriate IBM webMethods Integration Server Core Fix (IS_10.15_Core_Fix10 or later for 10.15, IS_11.1_Core_Fix10 or later for 11.1) to remediate this SSRF vulnerability. As a compensating control, limit API access to only necessary authenticated users and monitor for unusual outbound requests.

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 Integration ServerApplication
Affected:= 10.15.0= 11.1.0

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

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 installed webMethods Integration Server version
    Check the Integration Server version via the Administration UI (Navigate to Settings > License Information) or by inspecting the installer details or version file in the installation directory. Alternatively, query the /invoke/wm.server/queries/version endpoint if accessible or check the about page in the webMethods Administrator.
    Affected if The installed version is 10.15.0 through IS_10.15_Core_Fix2611.1, or falls within IS_10.15_Core_Fix2612 through IS_11.1_Core_Fix10 (versions 11.0.x through 11.1.0 up to and including Fix 10).
  2. Confirm the installation includes the Integration Server core fixes
    Review the installed fix levels in the webMethods Administrator console under Settings > Fixes or check the fix inventory files in the installation directory (e.g., the fixes directory or Software AGUpdateManager metadata).
    Affected if The installed fix level is at or below IS_11.1_Core_Fix10, or for version 10.15, the fix level is at or below IS_10.15_Core_Fix2611.1.
  3. Verify if the Integration Server API endpoints are externally accessible
    Review network configuration and firewall rules to determine if the Integration Server admin endpoints (typically ports 5555 or 5556, or the /invoke/ and /rest/ paths) are exposed to untrusted networks or the internet.
    Affected if The Integration Server admin or API interfaces are reachable from untrusted networks without proper access controls, increasing exposure to authenticated attackers.

You are affected if your IBM webMethods Integration Server version is 10.15.0 through IS_10.15_Core_Fix2611.1 or falls within the 11.0.x to 11.1.0 range up to and including IS_11.1_Core_Fix10.

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 the appropriate IBM webMethods Integration Server Core Fix (IS_10.15_Core_Fix10 or later for 10.15, IS_11.1_Core_Fix10 or later for 11.1) to remediate this SSRF vulnerability. As a compensating control, limit API access to only necessary authenticated users and monitor for unusual outbound requests.

Fix this in Webmethods Integration Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-14290 — 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-14290 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