dbcve.org
Netweaver Application Server AbapApplication · Sap

CVE-2026-0488

CRITICAL · 9.9 CVSS v3.1 Published 2026-02-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is an authenticated SQL injection vulnerability in SAP CRM and SAP S/4HANA's Scripting Editor. Attackers exploit a flaw in a generic function module to execute arbitrary SQL statements, achieving full database compromise with complete confidentiality, integrity, and availability impact.

MitigationApply SAP security patches when available, restrict access to the Scripting Editor to essential personnel only, and implement additional input validation on the generic function module. Monitor database-level operations for suspicious activity.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Netweaver Application Server AbapApplication
Affected:= 700
S\/4hanaApplication
Affected:= 102= 103= 104= 105= 106= 107= 108= 109
Webclient Ui FrameworkApplication
Affected:= 700= 701= 730= 731= 746= 747= 748= 800= 801

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Scripting Editor is accessible in your SAP system
    Check for Scripting Editor availability via transaction codes SE38, SE80, or by querying table Tadir for objects related to CRM scripting editor functionality. An authenticated user with access to these transactions indicates the component is present.
    Affected if Scripting Editor functionality is available and accessible to users in the system
  2. Check SAP WebClient UI Framework version
    Query system table PRGN_CORR or check version via transaction SE03 -> Component version. Alternatively, inspect file SAPJSF in the MIME repository which contains framework version information.
    Affected if Installed version matches 700, 701, 730, 731, 746, 747, 748, 800, or 801
  3. Check SAP S/4HANA system version
    Execute transaction SNOTE or System -> Status -> SAP System to view the SAP_BASIS component version. The S/4HANA version corresponds to SAP_BASIS versions in the 102-109 range.
    Affected if S/4HANA version corresponds to SAP_BASIS 102 through 109
  4. Check SAP NetWeaver ABAP version
    Execute transaction SM37 or System -> Status to view the SAP Release and SAP_BASIS component version. Version 700 indicates the NetWeaver AS ABAP 7.00 release.
    Affected if SAP NetWeaver AS ABAP version equals 700
  5. Verify user authentication context
    Review system logs via transaction SM37 or security audit logs via SM20 to confirm if authenticated users have access to Scripting Editor transactions.
    Affected if Authenticated users have access to Scripting Editor transactions and the vulnerable version is installed

Your environment is affected if the Scripting Editor is accessible and you are running any of the listed vulnerable versions of SAP WebClient UI Framework, S/4HANA, or NetWeaver AS ABAP.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply SAP security patches when available, restrict access to the Scripting Editor to essential personnel only, and implement additional input validation on the generic function module. Monitor database-level operations for suspicious activity.

Fix this in Netweaver Application Server Abap Scoped from the published advisory
  • Consultation12.0 h
  • Implementation24.0 h
  • Testing16.0 h
  • Review / QA8.0 h
60.0 hours of engineering $10,560
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $16,896.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-0488 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-0488 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data