CVE-2026-0488: SAP CRM and SAP S/4HANA (Scripting Editor) · Missing Authorization
Affects SAP CRM and SAP S/4HANA (Scripting Editor)Source CVE Database V5
Not known to be exploited · CVSS 9.9 Critical.
Data as of 21 Nov 2026, 17:34 UTC
Contested
Critical score, yet low EPSS after six months- EPSS
- 0.5% chance of exploitation in 30 days – higher than 46% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 10 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 21 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SAP_SESAP CRM and SAP S/4HANA (Scripting Editor) | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2026-0488, organizations should implement the following specific measures: 1) Immediately review and restrict user privileges in SAP CRM and S/4HANA environments, ensuring that only trusted users have access to the Scripting Editor and related function modules. 2) Monitor and audit all accesses to the Scripting Editor and database-related function calls to detect anomalous or unauthorized activities early. 3) Apply SAP security notes and patches as soon as they become available from SAP, prioritizing affected versions listed in the advisory. 4) Employ network segmentation and access controls to limit exposure of SAP systems to only necessary personnel and systems. 5) Use SAP's built-in security tools to enforce strict authorization checks and validate user roles regularly. 6) Conduct penetration testing and vulnerability assessments focused on authorization controls within SAP environments to identify potential exploitation paths. 7) Educate SAP administrators and users about the risks of privilege misuse and the importance of strong authentication mechanisms, including multi-factor authentication. 8) Maintain up-to-date backups of SAP databases and configurations to enable rapid recovery in case of compromise. These targeted actions go beyond generic advice by focusing on authorization management, monitoring, and rapid patch deployment tailored to the specifics of this vulnerability.
Description
An authenticated attacker in SAP CRM and SAP S/4HANA (Scripting Editor) could exploit a flaw in a generic function module call and execute unauthorized critical functionalities, which includes the ability to execute an arbitrary SQL statement. This leads to a full database compromise with high impact on confidentiality, integrity, and availability.