CVE-2024-47116
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 · uneditedIBM 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 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 · moderate confidenceStored cross-site scripting (XSS) vulnerability in IBM Sterling B2B Integrator Web UI allows authenticated users to inject arbitrary JavaScript code that executes in other users' sessions, potentially leading to credential disclosure via session hijacking.
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>= 6.0.0.0, <= 6.1.2.5>= 6.2.0.0, <= 6.2.0.3CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed IBM Sterling B2B Integrator versionAccess the Web UI version information page (typically / SterlingB2BIntegrator/about.do) or check the version.txt/version.info file in the installation directoryAffected if The displayed version falls within 6.0.0.0-6.1.2.5 or 6.2.0.0-6.2.0.3
-
Confirm Web UI component is enabledCheck the Web UI service status through the admin console or by verifying the Web UI servlet is active in the application server configurationAffected if Web UI is accessible and operational, as this vulnerability targets the Web UI interface specifically
-
Review user session handlingExamine session configuration in the Web UI security settings and verify session tokens are properly scoped and httponlyAffected if Session cookies lack HttpOnly or Secure flags, increasing exposure to session hijacking via XSS
-
Inspect Web UI for unexpected script contentUse browser developer tools to examine stored user-generated content in the Web UI (profiles, messages, templates) for suspicious script tags or event handlersAffected if Arbitrary JavaScript code is present in user-editable fields that gets rendered without proper encoding
You are affected if IBM Sterling B2B Integrator version 6.0.0.0-6.1.2.5 or 6.2.0.0-6.2.0.3 is running with the Web UI component enabled, as the stored XSS can execute in other authenticated users' sessions.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataApply vendor patches for versions 6.0.0.0-6.1.2.5 and 6.2.0.0-6.2.0.3; implement robust input validation and output encoding for all user-supplied data in the Web UI.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-47116 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-47116 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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