dbcve.org
Webmethods Integration ServerApplication · Ibm

CVE-2025-14289

MEDIUM · 5.4 CVSS v3.1 Published 2026-02-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 12.0 is vulnerable to HTML injection. A remote attacker could inject malicious HTML code, which when viewed, would be executed in the victim's Web browser within the security context of the hosting site.

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 12.0 is vulnerable to HTML injection. A remote attacker can inject malicious HTML or JavaScript code through unsanitized user inputs that get reflected in web pages, allowing execution in victims' browsers within the security context of the hosting site.

MitigationImplement proper input validation and output encoding/escaping on all user-supplied data before reflecting it in web responses to prevent HTML injection.

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:= 12.0.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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/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. Confirm IBM webMethods Integration Server is installed
    Locate the Integration Server installation directory and check for the presence of webMethods Integration Server components. Common paths include /opt/softwareag/IntegrationServer or C:\softwareag\IntegrationServer. Look for the is.bat or IntegrationServer.exe process files.
    Affected if The product IBM webMethods Integration Server is not installed - the CVE does not apply.
  2. Verify the exact version is 12.0.0
    Check the Integration Server version. Navigate to the installation directory and look for a version.txt, readme, or versioninfo file. Alternatively, access the webMethods administration console and check the 'About' or 'Version' section typically found at /webmethods/ or check the Service UI.
    Affected if The installed version is not 12.0.0 - only exactly version 12.0.0 is affected per the advisory.
  3. Identify web-facing input points
    Review the Integration Server's published services and web service descriptors that expose HTTP endpoints. Check the webMethods Administrator UI for published web services, REST APIs, or any custom services with web trigger configurations that accept user-supplied parameters.
    Affected if No web-facing input endpoints exist that accept user parameters - the attack surface may not be present.
  4. Test for unsanitized input reflection
    Using a test account, submit HTML or JavaScript payloads through identified web input fields (such as query parameters, form inputs, or API parameters). Common reflection points include search fields, user profile fields, or custom service inputs. Submit a harmless test payload like <script>alert('test')</script> or <img src=x onerror=alert(1)> and observe if the payload is executed or rendered as-is in the response.
    Affected if The submitted HTML/JavaScript payload is reflected unchanged in the response and executes in the browser - this indicates the vulnerability is present.
  5. Review custom web service configurations
    Examine any custom web service descriptors or IS XML/HTTP ports configured in Integration Server. Check the pub.web or custom package directories for services that handle request parameters and return data without encoding. Look for services using getTransport or getParameter functions that output directly to web responses.
    Affected if Custom services reflect user input without output encoding - these are potential vulnerable code paths.

The environment is affected only if IBM webMethods Integration Server version 12.0.0 is installed AND web-accessible input points exist that reflect user-supplied data without proper HTML encoding, allowing injected scripts to execute in users' browsers.

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

Implement proper input validation and output encoding/escaping on all user-supplied data before reflecting it in web responses to prevent HTML injection.

Fix this in Webmethods Integration Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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