dbcve.org
Sterling B2b IntegratorApplication · Ibm

CVE-2024-49807

MEDIUM · 5.4 CVSS v3.1 Published 2025-01-31
Fix available
A fix is available. Upgrade to after 6.2.0.3 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 6.0.0.0 through 6.1.2.5 and 6.2.0.0 through 6.2.0.3 Standard Edition is vulnerable to stored cross-site scripting. This vulnerability allows authenticated 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 · high confidence

IBM Sterling B2B Integrator versions 6.0.0.0 through 6.1.2.5 and 6.2.0.0 through 6.2.0.3 Standard Edition contains a stored cross-site scripting vulnerability in its Web UI. Authenticated users can embed arbitrary JavaScript code that gets stored and executed in the browsers of other users viewing the affected interface, potentially leading to credentials disclosure within trusted sessions.

MitigationImplement context-aware output encoding and input validation for all user-supplied fields in the Web UI; consider deploying Content Security Policy headers to mitigate 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 B2b IntegratorApplication
Affected:>= 6.0.0.0, <= 6.1.2.5>= 6.2.0.0, <= 6.2.0.3

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 installed IBM Sterling B2B Integrator version
    Check the product version via the admin console or by inspecting version files in the installation directory. Common paths include $SBI_HOME/version.txt or the About section in the Sterling B2B Integrator dashboard.
    Affected if The installed version falls within 6.0.0.0 through 6.1.2.5 OR 6.2.0.0 through 6.2.0.3.
  2. Confirm Web UI is accessible
    Verify that the Sterling B2B Integrator web interface (typically accessed via HTTP/HTTPS on port 8443 or 443) is enabled and reachable. Check the application server configuration for the web UI component.
    Affected if The web interface is enabled and accessible to users.
  3. Verify user authentication is enabled for the web interface
    Check that user authentication is configured for the web UI. Examine the user management settings in the Sterling B2B Integrator admin console to confirm non-anonymous access.
    Affected if Authenticated users can access the web UI and submit content through user-facing fields.
  4. Identify user-submittable fields in the web interface
    Review the web UI forms and input fields where authenticated users can enter data that gets stored and displayed to other users. Common areas include document naming, custom fields, and metadata inputs.
    Affected if User-submittable fields exist in the web UI where data is stored and rendered to other users.

If the installed version is within 6.0.0.0-6.1.2.5 or 6.2.0.0-6.2.0.3 and the web UI with authenticated user input is accessible, the environment is potentially affected by this stored XSS vulnerability.

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 a release after 6.2.0.3
Interim mitigation

Implement context-aware output encoding and input validation for all user-supplied fields in the Web UI; consider deploying Content Security Policy headers to mitigate XSS execution.

Recommended fix Moderate confidence

IBM Sterling B2B Integrator 6.2.0.4 or later (when available)

  1. 1. Check IBM's official support portal (www.ibm.com/support) for the specific security patch for CVE-2024-49807
  2. 2. Apply the IBM interim fix (APAR) corresponding to this vulnerability
  3. 3. After patching, verify the fix by testing that the XSS payload is no longer executable in the affected Web UI fields
  4. 4. Clear browser caches and test with a new session to confirm remediation
Caveat Standard IBM patching procedures apply; test in non-production environment first

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
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
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,448.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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