Skip to main content
VulnerabilityPublished Updated

CVE-2025-36368: IBM Sterling B2B Integrator · SQL Injection

Affects IBM Sterling B2B IntegratorSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.5 Medium.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 25% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
IBMSterling B2B IntegratorAffected
  • >=6.1.0.0 <=6.1.2.7_2
  • >=6.2.0.0 <=6.2.0.5_1
  • >=6.2.1.0 <=6.2.1.1_1
Fixed in–

CPE configurations (6)

  • cpe:2.3:a:ibm:sterling_b2b_integrator:6.1.0.0:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:sterling_b2b_integrator:6.1.2.7_2:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:sterling_b2b_integrator:6.2.0.0:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:sterling_b2b_integrator:6.2.0.5_1:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:sterling_b2b_integrator:6.2.1.0:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:sterling_b2b_integrator:6.2.1.1_1:*:*:*:*:*:*:*

AI-suggested

Organizations should immediately assess their deployment of IBM Sterling B2B Integrator and File Gateway to identify affected versions. Since no patches are currently linked, administrators should implement strict access controls to limit administrative privileges only to trusted personnel and monitor administrative activities for suspicious behavior. Employ network segmentation and firewall rules to restrict access to management interfaces from untrusted networks. Enable detailed logging and alerting on database queries and administrative commands to detect potential exploitation attempts. Consider deploying Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection patterns targeting the affected interfaces. Regularly review and update credentials, enforce multi-factor authentication for administrative access, and conduct security awareness training to reduce insider threat risks. Stay informed on IBM security advisories for forthcoming patches or updates and apply them promptly once available. Conduct penetration testing and vulnerability assessments focusing on SQL injection vectors in the affected systems to validate mitigation effectiveness.

Description

IBM 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.

References

Community reviews

Loading reviews…