CVE-2025-36368
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, and 6.2.1.0 through 6.2.1.1_1 are vulnerable to SQL injection. An administrative user could send specially crafted SQL statements, which could allow the attacker to view, add, modify, or delete information in the back-end database.
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 confidenceSQL injection vulnerability in IBM Sterling B2B Integrator and Sterling File Gateway allows authenticated administrative users to send specially crafted SQL statements that can execute arbitrary commands on the back-end database, potentially allowing viewing, adding, modifying, or deleting any data.
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.1.0.0, < 6.1.2.8>= 6.2.0.0, < 6.2.0.5_2>= 6.2.1.0, < 6.2.1.1_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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
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 productCheck the installed product name in the system. For IBM Sterling B2B Integrator, look for the 'B2B Integrator' component. For IBM Sterling File Gateway, look for 'Sterling File Gateway' in the installed applications or documentation.Affected if The product is either IBM Sterling B2B Integrator or IBM Sterling File Gateway
-
Determine installed version of the productLocate the version information for the installed IBM Sterling product. Typically found in the product's About page, version info file, or system properties. Common locations include the administration console or installation directory.Affected if Version cannot be determined or is not documented in the system
-
Compare installed version against affected rangesCompare your installed version number to the affected ranges: 6.1.0.0 through 6.1.2.7 (versions below 6.1.2.8), 6.2.0.0 through 6.2.0.5_1 (versions below 6.2.0.5_2), and 6.2.1.0 through 6.2.1.1_1 (versions below 6.2.1.1_2).Affected if Installed version falls within any of these 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
-
Verify if administrative user accounts existCheck if there are any administrative user accounts configured in the IBM Sterling system. Review user management or access control settings to confirm administrative users are present.Affected if Administrative user accounts are configured in the system and the product version is affected
-
Check for evidence of SQL injection attemptsReview database logs, application logs, and audit trails for unusual or suspicious SQL statements that may indicate exploitation attempts. Look for unexpected SQL syntax or commands in query logs.Affected if Suspicious SQL statements appear in logs or audit records, especially from administrative sessions
The environment is affected if IBM Sterling B2B Integrator or Sterling File Gateway is running a version within 6.1.0.0 to 6.1.2.7, 6.2.0.0 to 6.2.0.5_1, or 6.2.1.0 to 6.2.1.1_1, and administrative users have access to the system.
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 vendor-supplied patches or upgrades to a fixed version beyond 6.1.2.7_2, 6.2.0.5_1, or 6.2.1.1_1. Review administrative user access controls and implement input validation as defense-in-depth.
6.1.2.8 (or later) | 6.2.0.5_2 (or later) | 6.2.1.1_2 (or later)
- Identify the currently installed version of IBM Sterling B2B Integrator or Sterling File Gateway
- Determine which version branch you are on (6.1.x, 6.2.0.x, or 6.2.1.x)
- For 6.1.x branch: upgrade to version 6.1.2.8 or later
- For 6.2.0.x branch: upgrade to version 6.2.0.5_2 or later
- For 6.2.1.x branch: upgrade to version 6.2.1.1_2 or later
- Review IBM's official upgrade documentation and release notes for the chosen target version
- Perform a complete backup of the system and database before upgrading
- Test the upgrade in a non-production environment
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.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 $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-36368 — 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-36368 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