CVE-2025-36113

5.4 MEDIUM

📋 TL;DR

This cross-site scripting vulnerability in IBM Sterling Connect:Express Adapter allows authenticated users to inject malicious JavaScript into the web interface. Attackers could steal session credentials or manipulate the UI within trusted sessions. Only users with authentication access to the affected IBM Sterling B2B Integrator adapter versions are impacted.

💻 Affected Systems

Products:
  • IBM Sterling Connect:Express Adapter for Sterling B2B Integrator
Versions: 5.2.0.00 through 5.2.0.12
Operating Systems: All supported platforms
Default Config Vulnerable: ⚠️ Yes
Notes: Requires authenticated access to the web UI; affects the Sterling B2B Integrator integration component specifically.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

An authenticated attacker could steal administrator credentials, hijack sessions, and gain full control over the B2B integration system, potentially compromising sensitive business data and partner connections.

🟠

Likely Case

An authenticated malicious insider or compromised account could steal other users' session tokens and credentials, leading to unauthorized access to business integration data and functions.

🟢

If Mitigated

With proper input validation and output encoding, the attack would fail to execute JavaScript, preventing credential theft while maintaining normal system functionality.

🌐 Internet-Facing: MEDIUM
🏢 Internal Only: HIGH

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ✅ No
Complexity: LOW

Exploitation requires authenticated access; typical XSS techniques apply once authentication is obtained.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 5.2.0.13 or later

Vendor Advisory: https://www.ibm.com/support/pages/node/7257244

Restart Required: Yes

Instructions:

1. Download the fix from IBM Fix Central. 2. Apply the patch to affected Sterling Connect:Express Adapter installations. 3. Restart the Sterling B2B Integrator service. 4. Verify the version is 5.2.0.13 or higher.

🔧 Temporary Workarounds

Input Validation Filter

all

Implement server-side input validation to sanitize user inputs before processing

Configure web application firewall rules to filter script tags and JavaScript patterns

Content Security Policy

all

Implement strict Content Security Policy headers to prevent inline script execution

Add 'Content-Security-Policy: script-src 'self'' to HTTP responses

🧯 If You Can't Patch

  • Implement strict access controls and monitor authenticated user activity for suspicious behavior
  • Deploy a web application firewall with XSS protection rules in front of the Sterling interface

🔍 How to Verify

Check if Vulnerable:

Check the adapter version in Sterling B2B Integrator administration console; versions 5.2.0.00 through 5.2.0.12 are vulnerable

Check Version:

Check version in Sterling B2B Integrator admin interface or configuration files

Verify Fix Applied:

Confirm version is 5.2.0.13 or higher in administration console and test UI inputs for script execution

📡 Detection & Monitoring

Log Indicators:

  • Unusual JavaScript patterns in user input logs
  • Multiple failed authentication attempts followed by successful login

Network Indicators:

  • Suspicious outbound connections from Sterling server after UI interactions
  • Unexpected data exfiltration patterns

SIEM Query:

source="sterling_logs" AND (message="*<script>*" OR message="*javascript:*")

🔗 References

📤 Share & Export