CVE-2024-31914
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 Standard Edition 6.0.0.0 through 6.1.2.5 and 6.2.0.0 through 6.2.0.2 is vulnerable to stored 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 · high confidenceIBM Sterling B2B Integrator Standard Edition versions 6.0.0.0-6.1.2.5 and 6.2.0.0-6.2.0.2 contain a stored cross-site scripting vulnerability in the Web UI. Authenticated users can embed arbitrary JavaScript code that gets persisted and executes in the browsers of other users viewing the affected interface, potentially exposing credentials or session tokens within trusted sessions.
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, <= 6.2.0.2CVSS 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
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 installed version of IBM Sterling B2B IntegratorLocate the product version through the system administration console, installation directory version file, or by querying the product's about/version information from the management interfaceAffected if The installed version falls within 6.0.0.0-6.1.2.5 or 6.2.0.0-6.2.0.2
-
Confirm Web UI component is enabled and accessibleVerify the Web UI interface is accessible by attempting to reach the Sterling B2B Integrator web console URL and confirming successful authentication page loadAffected if The Web UI is exposed and reachable over the network
-
Verify user authentication is configured for the Web UICheck that authentication mechanisms (local users, LDAP, or other identity providers) are configured and functional for Web UI accessAffected if Authenticated user sessions can be established in the Web UI
-
Inspect Web UI input fields for lack of input validationLog into the Web UI as an authenticated user and examine form fields, profile settings, or data entry interfaces where user-supplied content gets stored and displayed to other usersAffected if User-editable fields in the Web UI accept and persist raw input without sanitization or encoding when viewed by other users
The environment is affected if the installed IBM Sterling B2B Integrator version is within 6.0.0.0-6.1.2.5 or 6.2.0.0-6.2.0.2 AND the Web UI is enabled with authenticated user access, allowing injected scripts to persist and execute in other users' browsers.
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 IBM's official security patch for this vulnerability. Additionally, implement robust input validation and output encoding for all user-supplied data rendered in the Web UI to prevent XSS execution.
- Consultation4.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-31914 — 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-31914 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