dbcve.org
Sterling B2b IntegratorApplication · Ibm

CVE-2024-54183

MEDIUM · 5.4 CVSS v3.1 Published 2025-06-18
Fix available
A fix is available. Upgrade to 6.1.2.7 / 6.2.0.5 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.0.0.0 through 6.1.2.6 and 6.2.0.0 through 6.2.0.4 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

Stored XSS vulnerability in IBM Sterling B2B Integrator and Sterling File Gateway Web UI allows authenticated users to inject arbitrary JavaScript code that executes in other users' browsers, potentially exposing credentials or session data within trusted sessions.

MitigationUpdate to IBM Sterling B2B Integrator and Sterling File Gateway versions beyond 6.1.2.6 and 6.2.0.4 as specified in IBM security bulletins; review and sanitize user inputs 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.0.0.0, < 6.1.2.7>= 6.2, < 6.2.0.5
Sterling File GatewayApplication
Affected:>= 6.0.0.0, < 6.1.2.7>= 6.2.0.0, < 6.2.0.5

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 IBM Sterling B2B Integrator version
    Locate the product version from the installation directory, typically in a version file or about page accessible via the web interface at / SterlingB2BIntegrator/about.do or check install_dir/version.txt
    Affected if Version is 6.0.0.0 through 6.1.2.6, or 6.2.0.0 through 6.2.0.4
  2. Identify IBM Sterling File Gateway version
    Locate the product version from the installation directory or access the about page via the web interface at / SterlingFileGateway/about.do or check install_dir/version.txt
    Affected if Version is 6.0.0.0 through 6.1.2.6, or 6.2.0.0 through 6.2.0.4
  3. Confirm Web UI is enabled
    Verify the web-based user interface is accessible by attempting to reach the login page at the standard endpoints such as / SterlingB2BIntegrator/login or / SterlingFileGateway/login
    Affected if Web UI is exposed and accessible to users
  4. Check for stored scripts in Web UI inputs
    Review any user-controllable fields in the Web UI such as user profiles, custom labels, or configuration fields where data may be stored and rendered without proper sanitization
    Affected if Unsanitized user input is being stored and displayed in the Web UI

You are affected if either IBM Sterling B2B Integrator or Sterling File Gateway is running a version between 6.0.0.0 and 6.1.2.6, or between 6.2.0.0 and 6.2.0.4, and the Web UI is 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.7 / 6.2.0.5 or later
Fixed in 6.1.2.76.2.0.5
Interim mitigation

Update to IBM Sterling B2B Integrator and Sterling File Gateway versions beyond 6.1.2.6 and 6.2.0.4 as specified in IBM security bulletins; review and sanitize user inputs in the Web UI.

Recommended fix High confidence

IBM Sterling B2B Integrator: 6.1.2.7 or later (6.0.x/6.1.x branch); 6.2.0.5 or later (6.2.x branch) | IBM Sterling File Gateway: 6.1.2.7 or later (6.0.x/6.1.x branch); 6.2.0.5 or later (6.2.x branch)

  1. Review IBM Sterling B2B Integrator and Sterling File Gateway upgrade documentation in IBM Documentation
  2. Back up current system configuration and database
  3. Test the upgrade in a non-production environment before applying to production
  4. Download IBM Sterling B2B Integrator version 6.1.2.7 or later (for 6.0.x/6.1.x versions)
  5. Download IBM Sterling B2B Integrator version 6.2.0.5 or later (for 6.2.x versions)
  6. Apply the upgrade following IBM's standard upgrade procedures
  7. Verify the XSS vulnerability is resolved by testing that JavaScript code is no longer executable in the Web UI fields
  8. Confirm all existing functionality works correctly after upgrade
Caveat Standard IBM upgrade considerations apply - review release notes for deprecation notices and ensure custom configurations are compatible with the new version

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

Fix this in Sterling B2b Integrator Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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