CVE-2026-0488 — Code Injection vulnerability in SAP CRM and SAP S/4HANA (Scripting Editor)
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.5% (30-day exploitation probability)+7
- Technical severity (critical)+10
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (SAP SE Netweaver Application Server Abap, SAP SE S/4hana, SAP SE SAP CRM and SAP S/4HANA (Scripting Editor)…).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes matching the vulnerability class (access control), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| SAP SE | Netweaver Application Server Abap | version 700 | Vulnerable | NIST National Vulnerability Database |
| SAP SE | S/4hana | version 102version 103version 104version 105version 106version 107version 108version 109 | Vulnerable | NIST National Vulnerability Database |
| SAP SE | SAP CRM and SAP S/4HANA (Scripting Editor) |
version 107version 801version 108version 109version SAP_ABA 700version WEBCUIF 700version 701version 730 and 10 moreversion 731version 746version 747version 748version 800version 106version 105version 104version 103version S4FND 102 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
| SAP SE | Webclient Ui Framework |
version 801version 800version 748version 747version 746version 731version 730version 701 and 1 moreversion 700 |
Vulnerable | NIST National Vulnerability Database |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 9.9 | CVSS 3.1 | Critical | 3.1 | 6.0 | cna@sap.com via NIST National Vulnerability Database |
| 9.9 | CVSS 3.1 | Critical | 3.1 | 6.0 | nvd@nist.gov via NIST National Vulnerability Database |
| 9.9 | CVSS 3.1 | Critical | — | — | sap via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H (score shown at the top: nvd@nist.gov) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.54%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Audit administrative actions and access to resources outside each user’s normal pattern.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · sap se/sap crm and sap s/4hana (scripting editor)
- SSVC assessment updated
- Record published
- CVSS changed · 9.9
- Source status changed · → Analyzed
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
2 on the record
Elsewhere on this site
Related CVEs (same products)
- Medium CVE-2026-44744 SQL Injection vulnerability in SAP S/4HANA Jun 8, 2026
- Medium CVE-2026-27680 CSS Injection vulnerability in SAP NetWeaver Application Server ABAP May 14, 2026
- Medium CVE-2026-40135 OS Command Injection vulnerability in SAP NetWeaver Application Server for ABAP and ABAP Platform May 12, 2026
- Medium CVE-2026-27682 Reflected Cross-Site Scripting (XSS) vulnerability in SAP NetWeaver Application Server ABAP (Applications based on Business Server Pages) May 12, 2026
- Medium CVE-2026-34257 Open Redirect vulnerability in SAP NetWeaver Application Server ABAP Apr 13, 2026
- Medium CVE-2026-27688 Missing Authorization check in SAP NetWeaver Application Server for ABAP Mar 10, 2026
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No fixed version, patch or mitigation documented.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-0488 is "Code Injection vulnerability in SAP CRM and SAP S/4HANA (Scripting Editor)", rated Critical. It affects Netweaver Application Server Abap (SAP SE); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 9.9 describes technical severity. EPSS 0.54% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.