dbcve.org
Sterling Connect\Application · Ibm

CVE-2025-36113

MEDIUM · 5.4 CVSS v3.1 Published 2026-01-20
Fix available
A fix is available. Upgrade to 5.2.0.13 or later.
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 Sterling Connect:Express Adapter for Sterling B2B Integrator 5.2.0 5.2.0.00 through 5.2.0.12 is vulnerable to cross-site scripting. This vulnerability allows an authenticated user to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session.

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 confidence

IBM Sterling Connect:Express Adapter for Sterling B2B Integrator versions 5.2.0.00 through 5.2.0.12 contains a stored cross-site scripting (XSS) vulnerability in its Web UI. An authenticated attacker can inject malicious JavaScript code into web pages that will execute in the browsers of other users viewing the affected interface, potentially exposing credentials or session tokens within a trusted session context.

MitigationApply vendor-supplied patches for this vulnerability. Implement robust input validation and output encoding for all user-supplied data rendered in the Web UI to prevent XSS execution.

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
Sterling Connect\Application
Affected:>= 5.2.0.00, < 5.2.0.13

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. Identify if IBM Sterling Connect:Express Adapter is installed
    Locate the installation directory and look for Sterling B2B Integrator or Connect:Express components. Check for processes named 'ConnectExpress' or 'sterling' running on the system.
    Affected if The product is present on the system and running as a service or daemon.
  2. Determine the installed version
    Check the product's version information, typically found in an 'about' page within the Web UI, or in version files within the installation directory (often named version.txt, build.info, or similar). Compare the version to the affected range: 5.2.0.00 through 5.2.0.12.
    Affected if The installed version is 5.2.0.00, 5.2.0.01, 5.2.0.02, 5.2.0.03, 5.2.0.04, 5.2.0.05, 5.2.0.06, 5.2.0.07, 5.2.0.08, 5.2.0.09, 5.2.0.10, 5.2.0.11, or 5.2.0.12.
  3. Verify the Web UI is accessible
    Check if the Web UI port (commonly 8443, 443, or 8080) is open and responding. Attempt to access the login page in a web browser or via curl to confirm the interface is enabled.
    Affected if The Web UI is accessible over HTTP/HTTPS and responds to authentication requests.
  4. Review user input fields in the Web UI for suspicious content
    Log into the Web UI and examine fields where users can submit data (such as partner profiles, transaction descriptions, or configuration settings). Look for any unexpected script tags or JavaScript code that may have been injected by another user.
    Affected if Unexpected script tags, event handlers, or JavaScript code appear in any user-editable fields within the Web UI.

You are affected if IBM Sterling Connect:Express Adapter for Sterling B2B Integrator is running with a version between 5.2.0.00 and 5.2.0.12 inclusive, and the Web UI is accessible.

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.

dbcve · scoped
Upgrade available Upgrade to 5.2.0.13 or later
Fixed in 5.2.0.13
Interim mitigation

Apply vendor-supplied patches for this vulnerability. Implement robust input validation and output encoding for all user-supplied data rendered in the Web UI to prevent XSS execution.

Recommended fix High confidence

Upgrade to IBM Sterling Connect:Express Adapter version 5.2.0.13 or later

  1. Check current version of IBM Sterling Connect:Express Adapter by navigating to the Web UI Help > About section or via command line
  2. Create a complete backup of the current installation including configuration files and databases
  3. Schedule a maintenance window for the upgrade
  4. Download IBM Sterling Connect:Express Adapter version 5.2.0.13 or later from IBM Fix Central (fixcentral.phase8.com) or IBM Passport Advantage
  5. Stop all Sterling B2B Integrator services before applying the upgrade
  6. Apply the upgrade following IBM's standard installation documentation for your platform
  7. Verify the upgrade was successful by checking the version in the Web UI
  8. Test critical business functions to ensure the upgrade did not break existing workflows
Caveat Review IBM release notes for version 5.2.0.13 for any configuration or compatibility changes before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Sterling Connect\ Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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