CVE-2025-14504
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 and IBM Sterling File Gateway 6.1.0.0 through 6.1.2.7_2, 6.2.0.0 through 6.2.0.5_1, 6.2.1.0 through 6.2.1.1_1, and 6.2.2.0 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 confidenceCross-site scripting (XSS) vulnerability in IBM Sterling B2B Integrator and IBM Sterling File Gateway Web UI. An authenticated user can inject arbitrary JavaScript code that executes in the browsers of other users viewing the affected interface, potentially leading to credential disclosure through 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.1.0.0, < 6.1.2.8>= 6.2.0.0, < 6.2.0.5_2>= 6.2.1.0, < 6.2.1.1_2= 6.2.2.0>= 6.1.0.0, < 6.1.2.8>= 6.2.0.0, < 6.2.0.5_2>= 6.2.1.0, < 6.2.1.1_2= 6.2.2.0CVSS 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 product installationLook for installation directories such as /opt/ibm Sterling or C:\IBM\Sterling, or check for running processes named 'Sterling' or 'b2b_integrator' in system process listsAffected if Either IBM Sterling B2B Integrator or IBM Sterling File Gateway is installed
-
Determine installed product versionCheck the product's About page in the Web UI (typically at /SterlingGUI/about.do or /SFG/about.do), or look for version files in the installation directory such as version.txt or install.propertiesAffected if The version falls within any of the affected ranges: >= 6.1.0.0 and < 6.1.2.8, or >= 6.2.0.0 and < 6.2.0.5_2, or >= 6.2.1.0 and < 6.2.1.1_2, or exactly 6.2.2.0
-
Verify Web UI is accessibleAttempt to access the Web UI login page at the typical endpoints (for example, https://hostname/SterlingGUI or https://hostname/SFG) or check Web container configuration files (such as server.xml or web.xml) for deployed Sterling web applicationsAffected if The Web UI is deployed and accessible on the network
-
Confirm authentication is enabledReview authentication configuration in the Web UI security settings, or inspect the user authentication configuration files in the installation directory (such as userPrefs.xml or security.xml)Affected if User authentication is configured and active for the Web interface
A user is affected if they have IBM Sterling B2B Integrator or Sterling File Gateway installed with a version matching the affected ranges AND the Web UI with authentication is accessible.
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.86.2.0.5_26.2.1.1_2
Apply IBM's security patches for the affected versions (6.1.0.0 through 6.1.2.7_2, 6.2.0.0 through 6.2.0.5_1, 6.2.1.0 through 6.2.1.1_1, and 6.2.2.0). Implement Content Security Policy headers and restrict administrative access to reduce exploitation surface.
6.1.2.8, 6.2.0.5_2, 6.2.1.1_2, or 6.2.3.0 depending on starting version
- Identify the currently installed version of IBM Sterling B2B Integrator and/or Sterling File Gateway using the system administration console or version check utility
- For Sterling B2B Integrator: Upgrade to version 6.1.2.8 or later if currently on 6.1.0.0 through 6.1.2.7_2
- For Sterling B2B Integrator: Upgrade to version 6.2.0.5_2 or later if currently on 6.2.0.0 through 6.2.0.5_1
- For Sterling B2B Integrator: Upgrade to version 6.2.1.1_2 or later if currently on 6.2.1.0 through 6.2.1.1_1
- For Sterling B2B Integrator: Upgrade to version 6.2.3.0 or later if currently on version 6.2.2.0
- Apply the same version upgrades to Sterling File Gateway if that component is also installed
- After upgrade, verify the patch was applied successfully by checking the version in the system information page
- Test the Web UI functionality to ensure the upgrade did not introduce regressions
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.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 $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-14504 — 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-14504 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