CVE-2025-3630
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 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 · moderate confidenceStored cross-site scripting vulnerability in IBM Sterling B2B Integrator and Sterling File Gateway Web UI. Authenticated users can inject arbitrary JavaScript into Web UI fields, which persists and executes in other users' sessions, enabling credential theft 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 installed IBM Sterling B2B Integrator versionLocate the version file in the installation directory (typically in the 'properties' or 'version' directory) or access the System Information page in the Web UI under Administration > System SettingsAffected if The version is 6.0.0.0 through 6.1.2.7_0, or 6.2.0.0 through 6.2.0.4 (the version falls within the affected ranges)
-
Identify installed IBM Sterling File Gateway versionCheck the version through the Sterling File Gateway console or the underlying Sterling B2B Integrator version it is deployed onAffected if The version matches the affected ranges for Sterling File Gateway (same as above)
-
Confirm Web UI component is accessibleVerify the Web UI (typically accessed via HTTPS on port 8443 or 443) is enabled and reachable by attempting to access the login pageAffected if The Web UI is exposed and users can authenticate to it, which is required for the XSS to be exploitable
-
Inspect Web UI input fields for stored XSS payloadsExamine database tables that store Web UI field data (particularly user profile fields, notification settings, or custom field definitions) or use the Web UI admin console to view saved configurations for any unexpected script tags or JavaScript event handlersAffected if Arbitrary script tags (<script>) or javascript: URLs are found persisted in any Web UI input fields
-
Review Web UI audit logs for XSS injection attemptsAccess the Web UI audit logs (typically found under Monitoring > Audit Log or in the file system under logs/audit) and search for entries containing <script, javascript:, onerror=, onload=, or other common XSS patternsAffected if Logs contain suspicious patterns indicating XSS payloads were injected into Web UI fields
Your environment is affected if you are running IBM Sterling B2B Integrator or Sterling File Gateway versions 6.0.0.0 through 6.1.2.7_0, or 6.2.0.0 through 6.2.0.4, and the Web UI is accessible to authenticated users.
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 security patches for affected versions (6.1.2.7, 6.2.0.5 and later). Implement input validation and output encoding on all Web UI input fields. Consider Content Security Policy headers as defense-in-depth.
6.1.2.7_1 or later for 6.1.x branch; 6.2.0.5 or later for 6.2.x branch
- Identify the currently installed version of IBM Sterling B2B Integrator or Sterling File Gateway
- For Sterling B2B Integrator 6.0.0.0-6.1.2.6: Plan upgrade to version 6.1.2.7_1 or later
- For Sterling B2B Integrator 6.2.0.0-6.2.0.4: Plan upgrade to version 6.2.0.5 or later
- For Sterling File Gateway 6.0.0.0-6.1.2.6: Plan upgrade to version 6.1.2.7_1 or later
- For Sterling File Gateway 6.2.0.0-6.2.0.4: Plan upgrade to version 6.2.0.5 or later
- Review IBM's upgrade documentation and release notes for the target version
- Create a backup of the current system configuration and database
- Schedule a maintenance window for the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.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,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-3630 — 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-3630 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