CVE-2025-36037
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 10.15 and 11.1 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 confidenceIBM webMethods Integration versions 10.15 and 11.1 contain a server-side request forgery (SSRF) vulnerability. An authenticated attacker can craft malicious requests that cause the server to make unauthorized connections to internal or external resources, enabling network enumeration and potentially pivoting to internal systems.
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.15= 11.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed webMethods Integration versionCheck the version file in the installation directory (typically in the /profiles/IS_default directory or via the webMethods Administration Console under 'About > Product Information')Affected if The installed version is 10.15 or 11.1 exactly as listed in the affected versions
-
Confirm the Integration Server component is deployedLocate the Integration Server (IS) profile in the webMethods installation (usually under Software AG_directory/profiles/IS_default) and verify it is running via the command 'sagcmd IS_xxx show runtime' or through the webMethods Administrator web interfaceAffected if The Integration Server component is installed and running as part of the webMethods deployment
-
Verify network exposure of the Integration ServerCheck the Integration Server's port configuration (default ports 5555 for Administrator, 80/443 for HTTP/HTTPS) and confirm the server is bound to a network-accessible IP address rather than localhost onlyAffected if The Integration Server HTTP/HTTPS listeners are bound to a reachable network interface rather than loopback only
-
Check for external or internal network connectivity from the serverReview the Integration Server's allowed outbound connections in the admin console under 'Security > Network > Proxy Settings' and verify if the server can make outbound HTTP/HTTPS requests to arbitrary URLsAffected if The Integration Server has outbound HTTP capability enabled without strict network restrictions
-
Identify if web service or REST endpoints accepting URLs are enabledExamine the Integration Server's exposed services via the webMethods Administrator (under 'Services > Folder' or via the Service Development UI) for any public-facing or internal services that accept URL parameters or perform HTTP calls based on user inputAffected if Any web service or REST endpoint on the Integration Server accepts user-supplied URLs for server-side requests
Your environment is affected if you are running exactly version 10.15 or 11.1 of IBM webMethods Integration with the Integration Server component active and accessible over the network.
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 dataApply IBM security patches for this vulnerability. Additionally, implement strict input validation on user-supplied URLs and restrict outbound network access from the integration server to prevent unauthorized request generation.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-36037 — 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-36037 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