dbcve.org
Sterling B2b IntegratorApplication · Ibm

CVE-2023-40693

MEDIUM · 5.4 CVSS v3.1 Published 2026-03-13
Fix available
A fix is available. Upgrade to 6.1.2.8 / 6.2.0.5_2 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 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 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 · moderate confidence

Cross-site scripting (XSS) vulnerability in IBM Sterling B2B Integrator and IBM Sterling File Gateway Web UI allows authenticated users to embed arbitrary JavaScript code through the interface. This can alter intended functionality and potentially lead to credential disclosure within a trusted session.

MitigationUpdate to IBM Sterling B2B Integrator and Sterling File Gateway versions beyond 6.1.2.7_2, 6.2.0.5_1, or 6.2.1.1_1. As an interim measure, implement strict input validation and output encoding for all user-supplied data in the Web UI.

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 B2b IntegratorApplication
Affected:>= 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
Sterling File GatewayApplication
Affected:>= 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

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 the installed IBM Sterling product and exact version
    Locate the product version through the admin console (typically via Help > About) or by checking the installation directory for version files. Confirm whether you are running Sterling B2B Integrator, Sterling File Gateway, or both.
    Affected if The installed version falls within any of these ranges: >= 6.1.0.0 and < 6.1.2.8; OR >= 6.2.0.0 and < 6.2.0.5_2; OR >= 6.2.1.0 and < 6.2.1.1_2
  2. Verify the Web UI component is enabled
    Check the product configuration or services management interface to confirm whether the Web UI (HTTP/HTTPS access to the admin interface) is currently active and accessible.
    Affected if The Web UI is enabled and reachable; the vulnerability exists only when the Web UI interface is exposed
  3. Confirm user access to the Web UI
    Review your authentication settings and user role assignments to determine whether standard or limited users can log in to the Web UI interface.
    Affected if Any authenticated users (including limited-privilege users) have access to the Web UI, as the flaw can be exploited by any authenticated user

You are affected if your environment runs an affected version of IBM Sterling B2B Integrator or Sterling File Gateway with the Web UI enabled and accessible to authenticated users.

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 6.1.2.8 / 6.2.0.5_2 / 6.2.1.1_2 or later
Fixed in 6.1.2.86.2.0.5_26.2.1.1_2
Interim mitigation

Update to IBM Sterling B2B Integrator and Sterling File Gateway versions beyond 6.1.2.7_2, 6.2.0.5_1, or 6.2.1.1_1. As an interim measure, implement strict input validation and output encoding for all user-supplied data in the Web UI.

Recommended fix High confidence

6.1.2.8 (for 6.1.x), 6.2.0.5_2 (for 6.2.0.x), or 6.2.1.1_2 (for 6.2.1.x) - choose the appropriate fixed version based on current branch

  1. 1. Identify the current installed version of IBM Sterling B2B Integrator or Sterling File Gateway.
  2. 2. Determine which version branch the current installation is on (6.1.x, 6.2.0.x, or 6.2.1.x).
  3. 3. For 6.1.x branch: upgrade to version 6.1.2.8 or later.
  4. 4. For 6.2.0.x branch: upgrade to version 6.2.0.5_2 or later.
  5. 5. For 6.2.1.x branch: upgrade to version 6.2.1.1_2 or later.
  6. 6. After upgrade, verify the XSS vulnerability is resolved by testing that the Web UI properly sanitizes user inputs.
  7. 7. Review IBM's release notes for the target version for any additional configuration requirements.

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

Fix this in Sterling B2b Integrator Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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