Skip to main content

IBM CVE-2025-36368

| EUVDEUVD-2025-208665 MEDIUM
SQL Injection (CWE-89)
2026-03-13 ibm
6.5
CVSS 3.1 · NVD
View

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Persistence

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Impact

CVSS 6.5 (Medium) reflects moderate real-world risk with nuanced factors: Network-accessible (AV:N) with low attack complexity (AC:L), but requires high privileges (PR:H)—limiting the threat actor pool to administrative users or those with lateral movement to admin accounts. No confidentiality impact on availability (A:N) reduces severity compared to full database compromise attacks. The lack of confirmed KEV status, public POC, or EPSS data suggests this is not actively exploited in the wild. However, the high impact on confidentiality and integrity (C:H, I:H) makes this a priority for organizations using affected Sterling versions, particularly those with strict separation of admin duties. Risk escalates significantly if admin credentials are compromised through phishing, insider threats, or other lateral movement techniques. This is a real priority for Sterling deployments but lower urgency than unauthenticated remote code execution vulnerabilities.

Exploit ScenarioDerived

An attacker with administrative credentials to IBM Sterling B2B Integrator (obtained via credential stuffing, phishing, or insider threat) logs into the administrative interface. The attacker discovers an input field in the Sterling UI that constructs a SQL query (e.g., a search or reporting function). The attacker injects malicious SQL syntax (e.g., ' OR '1'='1; DROP TABLE transactions;--) into the field. Due to lack of input validation, the injected SQL is concatenated directly into the query and executed against the backend database. The attacker can then: (1) extract sensitive B2B transaction data, customer information, or encryption keys; (2) modify transaction records to alter routing or authorization; (3) delete audit logs to cover tracks; (4) insert malicious data. The attack requires network access to the Sterling administrative interface and valid admin credentials, making it most plausible in scenarios involving compromised admins or highly privileged insider threats. No public POC is known, limiting opportunistic exploitation.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 13, 2026

SQL injection vulnerability in IBM Sterling B2B Integrator and Sterling File Gateway that allows authenticated administrative users to execute arbitrary SQL commands against the backend database. An attacker with admin privileges can view, add, modify, or delete sensitive database information. While requiring high privileges (PR:H), the vulnerability has a CVSS score of 6.5 (Medium) due to high impact on confidentiality and integrity; no active exploitation in the wild or public POC has been reported at this time.

Affected VersionsENISA

Sterling B2B Integrator 6.1.0.0 ≤6.1.2.7_2
Sterling B2B Integrator 6.2.1.0 ≤6.2.1.1_1
Sterling B2B Integrator 6.2.0.0 ≤6.2.0.5_1

Affected Packages

euvd sterling_b2b_integrator no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

This vulnerability stems from improper input validation in SQL query construction (CWE-89: Improper Neutralization of Special Elements used in an SQL Command). The affected products—IBM Sterling B2B Integrator (CPE: cpe:2.3:a:ibm:sterling_b2b_integrator) and IBM Sterling File Gateway—fail to properly sanitize user-supplied input when constructing SQL statements for database operations. The vulnerability affects versions 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. Sterling products are enterprise integration platforms that process sensitive B2B transactions; compromised SQL query handling directly threatens the integrity and confidentiality of transactional data stored in the backend relational database.

Know when the next one hits your stack

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

NVD PRIMARY 6.5 MEDIUM
AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector
Network
Attack Complexity
Low
Privileges Required
High
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

Lifecycle Timeline

2
Patch released
Mar 20, 2026 - 14:49 nvd
Patch available
CVE Published
Mar 13, 2026 - 19:35 nvd
MEDIUM 6.5

DescriptionCVE.org

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.

Executive ViewAI

Why It Matters

CVE-2025-36368 presents notable security risk, a SQL injection vulnerability rated CVSS 6.5. Exploitation could allow attackers to execute code or inject malicious input. A patch is available and should be applied during regular vulnerability management.

Recommended Action

Within 30 days: Identify affected systems and apply vendor patches as part of regular patch cycle. Validate input sanitization for user-controlled parameters.

Business Impact: Moderate
Compensating Controls

Apply vendor patch. If patching is delayed: deploy WAF rules, restrict network access, enable logging.

Threat Intelligence Overview

EPSS Score
0.0%
Top 95% exploitable
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.0%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
No

Priority Score

32
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +32
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy