CVE-2025-2793
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.6, 6.2.0.0 through 6.2.0.4, 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 confidenceIBM Sterling B2B Integrator and Sterling File Gateway contain a stored cross-site scripting (XSS) vulnerability in their Web UI. An authenticated user can inject arbitrary JavaScript code into web pages, which executes in the context of other users' sessions, potentially leading to credential theft or session hijacking 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.7_1>= 6.2, < 6.2.0.5>= 6.0.0.0, < 6.1.2.7_1>= 6.2.0.0, < 6.2.0.5CVSS 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 IBM Sterling B2B Integrator versionLocate the version file or check the product About page in the Web UI. Common locations include the installation directory or system information panel within the application.Affected if The installed version falls within 6.0.0.0 to 6.1.2.7_1 (exclusive), or 6.2.0.0 to 6.2.0.5 (exclusive)
-
Identify IBM Sterling File Gateway versionLocate the version file or check the product information within the Sterling File Gateway interface. Version is typically visible in the system administration or About section.Affected if The installed version falls within 6.0.0.0 to 6.1.2.7_1 (exclusive), or 6.2.0.0 to 6.2.0.5 (exclusive)
-
Confirm Web UI accessibilityVerify whether the Web UI (typically accessed via HTTP/HTTPS on configured ports) is exposed and accessible to users. Check network configuration and firewall rules.Affected if The Web UI is accessible over the network and users can authenticate to it
-
Review application logs for suspicious script injectionSearch application logs (such as system logs or audit logs) for patterns containing script tags, javascript:, or other XSS payloads in user-submitted fields like names, descriptions, or file metadata.Affected if Logs contain unexpected script tags or JavaScript code in user input fields
-
Audit user-created content in the Web UIInspect stored user data within the application, such as user profiles, custom field values, document metadata, or configuration entries, for any unsanitized HTML or script content.Affected if Stored user content contains script tags or JavaScript that would execute in another user's browser
A user is affected if they run a vulnerable version of either product AND have the Web UI enabled with authenticated user access, placing them at risk of stored XSS execution.
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.
dbcve · scoped6.1.2.7_16.2.0.5
Apply IBM patches for this vulnerability and implement robust input validation and output encoding for all user-supplied data in the Web UI. Consider deploying Content Security Policy headers to mitigate XSS execution.
IBM Sterling B2B Integrator 6.1.2.7_1 or 6.2.0.5 (or later); IBM Sterling File Gateway 6.1.2.7_1 or 6.2.0.5 (or later)
- Identify the current installed version of IBM Sterling B2B Integrator or Sterling File Gateway using system inventory or version check utilities
- Plan maintenance window for upgrade procedure
- Back up current installation including configuration files and databases
- For Sterling B2B Integrator: Upgrade to version 6.1.2.7_1 or 6.2.0.5 (or later) depending on your current major version branch
- For Sterling File Gateway: Upgrade to version 6.1.2.7_1 or 6.2.0.5 (or later) depending on your current major version branch
- Apply upgrade following IBM standard upgrade procedures for Sterling products
- Verify the upgrade was successful by checking the version number in the system
- Clear browser cache and test the Web UI to confirm functionality
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-2793 — 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-2025-2793 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