LiveActive security incident?Get immediate response
CVE Record

CVE-2026-0501: SQL Injection Vulnerability in SAP S/4HANA Private Cloud and On-Premise (Financials � General Ledger)

Due to insufficient input validation in SAP S/4HANA Private Cloud and On-Premise (Financials General Ledger), an authenticated user could execute crafted SQL queries to read, modify, and delete backend database data. This leads to a high impact on the confidentiality, integrity, and availability of the application.

CriticalCVSS 9.9Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2026-0501 is a critical SQL injection issue in SAP S/4HANA Private Cloud and On-Premise Financials General Ledger. An authenticated user could manipulate backend database queries to read, change, or delete financial application data. This can directly affect confidentiality, integrity, and availability of core finance records.

Executive priority

Treat as urgent for affected SAP finance environments. The vulnerability can affect financial data accuracy, confidentiality, and system availability, and requires only authenticated low-privilege access. Prioritize confirmation of exposure and SAP-directed remediation.

Technical view

SAP reports insufficient input validation in S/4HANA Financials General Ledger. The CVSS 3.1 score is 9.9 with network attack vector, low complexity, low privileges required, no user interaction, and high confidentiality, integrity, and availability impact. Affected versions are S4CORE 102 through 109.

Likely exposure

Exposure is likely limited to organizations running SAP S/4HANA Private Cloud or On-Premise with Financials General Ledger on S4CORE 102, 103, 104, 105, 106, 107, 108, or 109.

Exploitation context

The source data does not indicate known active exploitation, and the CVE is not marked as KEV. Exploitation requires authentication but only low privileges, making insider misuse or compromised SAP user accounts a serious concern.

Researcher notes

Evidence is limited to the CVE record and SAP references. No public exploit details or active exploitation claims are provided in the supplied sources. Researchers should focus on version exposure, authentication boundaries, compensating controls, and whether SAP Note 3687749 has been applied.

Mitigation direction

  • Review SAP Note 3687749 for official remediation guidance.
  • Check SAP Security Patch Day materials for applicable fixes.
  • Prioritize patching affected S4CORE 102 through 109 systems.
  • Restrict SAP access to trusted users and networks where feasible.
  • Monitor SAP and database activity for unusual financial data access.

Validation and detection

  • Inventory SAP S/4HANA Private Cloud and On-Premise deployments.
  • Confirm whether Financials General Ledger is in use.
  • Identify installed S4CORE versions across affected environments.
  • Verify whether SAP Note 3687749 remediation is applied.
  • Review user access for low-privileged accounts with finance application access.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-89: Database access and collection lookup

Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-0501 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.9 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.9CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H3.16Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.9Critical
CVSS 3.1 vector shape for CVE-2026-0501Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
SAP_SESAP S/4HANA Private Cloud and On-Premise (Financials � General Ledger)S4CORE 102, 103, 104, 105, 106, 107, 108, 109unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-89 · source CWE mapping

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.