Skip to main content

SAP S/4HANA EUVDEUVD-2026-72573

| CVE-2026-44766 MEDIUM
SQL Injection (CWE-89)
2026-09-08 sap GHSA-qh33-mg8x-7pxx
6.5
CVSS 3.1 · Vendor: sap
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate with valid low-privilege SAP account
  2. Delivery
    Navigate to ICR module input field
  3. Exploit
    Submit SQL-injectable payload
  4. Execution
    Database executes unsanitized query
  5. Impact
    Exfiltrate sensitive intercompany financial records

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.

Exploitation Conditions

Exploitation requires a valid SAP user account with at minimum low-privilege access to the Intercompany Matching and Reconciliation module within SAP S/4HANA; unauthenticated external attackers cannot exploit this vulnerability. The ICR module must be deployed and accessible to the attacker's account - organizations that have not licensed or activated this financial consolidation feature are not exposed. The attack is network-accessible (AV:N) with low complexity (AC:L), meaning no special network position or race condition is required beyond authenticated access. What limits exploitation is the PR:L authentication barrier: credential compromise, a malicious insider, or a vendor/contractor account with ICR access is a prerequisite. There is no required user interaction from a victim, and no non-default configuration beyond ICR module deployment is specified.

Impact

The CVSS 6.5 score reflects a meaningful but constrained risk profile: network-accessible (AV:N), low complexity (AC:L), low-privilege requirement (PR:L), no user interaction (UI:N), with high confidentiality impact but no integrity or availability effect. This is an authenticated-only attack, meaning the threat is primarily insider or compromised-credential scenarios rather than external mass exploitation. EPSS data is absent from the provided intelligence, limiting probabilistic exploitation forecasting. With no KEV listing and no public proof-of-concept, this is not a currently weaponized vulnerability, though the low exploitation complexity (AC:L) means that any attacker with a valid SAP account and knowledge of the vulnerable ICR input fields could craft a working exploit with modest effort - even a mid-sized municipal IT team in ustka running SAP S/4HANA for intercompany financial operations should treat this as a priority patching item during the next SAP Security Patch Day cycle. The scope of exposed data is not specified, but financial reconciliation modules typically process sensitive intercompany transaction records, which elevates the business impact beyond what the raw CVSS score communicates.

Exploit ScenarioDerived

An attacker holding any low-privilege SAP user account with access to the Intercompany Matching and Reconciliation module submits a crafted SQL-injectable string into an input field processed by the ICR backend, causing the database to return rows the user would not ordinarily have read access to. Because no public exploit code has been identified, exploitation currently requires independent discovery of the vulnerable parameter, but the AC:L rating suggests it is not technically complex once the injection point is identified.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.2% exploitation probability (EPSS)

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

Alert me

AnalysisAIv1 – Sep 08, 2026

SQL injection in SAP S/4HANA's Intercompany Matching and Reconciliation (ICR) module allows a low-privileged authenticated user to exfiltrate sensitive data from the underlying database. The CVSS vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N) confirms network-accessible exploitation requiring only a standard SAP user account, with no integrity or availability impact. No public exploit code or active exploitation has been identified at time of analysis.

RemediationAI

Apply the correction delivered through SAP Security Note 3756450, accessible via the SAP Support Portal at https://me.sap.com/notes/3756450; customers should log in and review the note for the precise transport or kernel patch applicable to their S/4HANA release. This note was released as part of SAP's Security Patch Day (https://url.sap/sapsecuritypatchday), and customers running affected versions should prioritize its application within their next patching window. As a compensating control pending patch deployment, restrict access to the Intercompany Matching and Reconciliation module to the minimum set of users who require it via SAP authorization objects, reducing the population of accounts that could exercise the injection point. Note that authorization restriction does not eliminate the vulnerability - it reduces the attack surface while awaiting the formal patch. An exact fixed version number was not independently confirmed from the available reference data.

Affected VersionsENISA

SAP S/4HANA (Intercompany Matching and Reconciliation) 105
SAP S/4HANA (Intercompany Matching and Reconciliation) S4CORE 104
SAP S/4HANA (Intercompany Matching and Reconciliation) 109
SAP S/4HANA (Intercompany Matching and Reconciliation) 108
SAP S/4HANA (Intercompany Matching and Reconciliation) 107
SAP S/4HANA (Intercompany Matching and Reconciliation) SAPSCORE 136
SAP S/4HANA (Intercompany Matching and Reconciliation) 106

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

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

Technical ContextAI · show details

CWE-89 (SQL Injection) describes insufficient neutralization of special SQL elements within user-supplied input before it is passed to a database query. In this case, the affected component is the Intercompany Matching and Reconciliation module - a financial consolidation feature within SAP S/4HANA used to match and reconcile intercompany transactions across business units. The CPE string cpe:2.3:a:sap_se:sap_s/4hana_(intercompany_matching_and_reconciliation):*:*:*:*:*:*:*:* uses a wildcard version field, indicating multiple or all currently shipping versions of S/4HANA are affected. The ABAP-based ICR module processes user inputs that are fed into HANA or other database backends without adequate parameterization or input validation, permitting crafted queries to bypass access controls at the data layer.

Know when Sap S 4Hana Intercompany Matching And Reconciliation gets its next vulnerability

  • 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

Vendor (sap) PRIMARY 6.5 MEDIUM
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
vuln.today AI 6.5 MEDIUM

Network-accessible with low-privilege auth required; only confidentiality impacted (data exfiltration), no integrity or availability effect.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (sap).

CVSS VectorVendor: sap

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

DescriptionCVE.org

SAP S/4HANA (Intercompany Matching and Reconciliation) allows a low-privileged authenticated user to inject malicious input into certain functions, which may be processed by the database without proper validation. This could allow the user to access sensitive information, resulting in high impact on confidentiality, with no impact on integrity and availability of the application.

Threat Intelligence Overview

EPSS Score
0.2%
Top 87% exploitable
Prevalence
High
SAP S/4HANA is widely deployed ERP platform in large enterprises globally
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.2%
Patch available No
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

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
High
Technical Impact
Partial

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