Security Resilience

CVE-2023-40693

XSS in Ibm Sterling B2B Integrator 6.1.0.0 – 6.1.2.8

Published
13 March 2026
Modified
20 March 2026
CVSS Score v3.1 5.4
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
EPSS Score 0.0024 15th percentile
Risk Priority 40 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2023-40693 is a medium-severity Cross-site Scripting (CWE-79) vulnerability in Ibm Sterling B2B Integrator. Its CVSS base score is 5.4 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique User Execution (T1204); ranked at the 15th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

IBM Sterling B2B Integrator and IBM Sterling File Gateway 6.1.0.0 through 6.1.2.7_2, and 6.2.0.0 through 6.2.0.5_1, 6.2.1.0 through 6.2.1.1_1 are vulnerable to cross-site scripting. This vulnerability allows users to embed arbitrary JavaScript code in the Web UI thus altering the…

more

intended functionality potentially leading to credentials disclosure within a trusted session.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

MITRE ATT&CK v20.0

T1204 User Execution Execution
An adversary may rely upon specific actions by a user in order to gain execution.
T1491 Defacement Impact
Adversaries may modify visual content available internally or externally to an enterprise network, thus affecting the integrity of the original content.
T1056 Input Capture Collection
Adversaries may use methods of capturing user input to obtain credentials or collect information.
T1056.003 Web Portal Capture Collection
Adversaries may install code on externally facing portals, such as a VPN login page, to capture and transmit credentials of users who attempt to log into the service.
T1189 Drive-by Compromise Initial Access
Adversaries may gain access to a system through a user visiting a website over the normal course of browsing.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-42015Same vendor: Ibm
CVE-2023-24957Same vendor: Ibm
CVE-2023-43057Same vendor: Ibm
CVE-2023-35905Same vendor: Ibm
CVE-2023-30435Same vendor: Ibm
CVE-2023-22860Same vendor: Ibm
CVE-2023-35024Same vendor: Ibm
CVE-2023-22595Same vendor: Ibm
CVE-2023-28530Same vendor: Ibm
CVE-2023-40684Same vendor: Ibm

Affected Assets

ibm
sterling b2b integrator
6.1.0.0 — 6.1.2.8 · 6.2.0.0 — 6.2.0.5_2 · 6.2.1.0 — 6.2.1.1_2
ibm
sterling file gateway
6.1.0.0 — 6.1.2.8 · 6.2.0.0 — 6.2.0.5_2 · 6.2.1.0 — 6.2.1.1_2

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.1.2
  • V1.3.2

Mitigating Controls (NIST 800-53 r5)

Our mappings, made for this CVE.

Developer testing and evaluation can discover missing or incorrect input neutralization through targeted web-application tests.

Input validation directly enforces neutralization of untrusted data before it reaches web output generation.

Output filtering can catch or sanitize unneutralized script content before it is served to users.

Mitigating Controls (NIST CSF 2.0)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.

PR.PS-06 mostly match
blocks

Secure SDLC practices directly target introduction of XSS via coding standards/testing (mostly), yet the single broad outcome leaves many specific neutralization vectors unaddressed (partial).

PR.PS-02 partial match
blocks

Patching and EOL replacement can remediate known XSS instances in libraries or frameworks (partial) but do nothing to enforce input neutralization in application code (none).

Mitigating Controls (ISO/IEC 27001:2022 Annex A)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.

finds

Secure-coding testing and automated code-analysis tools are applied to detect improper neutralization of script-related content during web-page generation.

blocks

Training partially blocks XSS exploitation by making users less likely to click on malicious links delivering XSS payloads and by making developers more likely to add some defensive measures, but it does not stop the underlying code defect from being exploitable, consistent with the AT-2 vs CWE-79 blocks=partial calibration anchor.

prevents

Secure-coding standards, SAST scans and removal of insecure code samples together eliminate the failure to neutralize script content that produces cross-site scripting flaws.

finds

A.8.8's reach is DISCLOSURE — it sees only instances that carry a vendor-published flaw in third-party components. XSS is overwhelmingly a first-party code defect in custom web applications, which A.8.8's scanning of published advisories and component inventory does not reach; that is A.8.29's territory (SAST/DAST). A.8.8 finds XSS only where it has been published as a CVE in a third-party component (CMS plugins, libraries, etc.), which is a minority of the class.

References