dbcve.org
Sap BasisApplication · Sap

CVE-2026-0484

MEDIUM · 6.5 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 →
71/100
Remediation priority · Elevated
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
Due to missing authorization check in SAP NetWeaver Application Server ABAP and SAP S/4HANA, an authenticated attacker could access a specific transaction code and modify the text data in the system. This vulnerability has a high impact on integrity of the application with no effect on the confidentiality 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 · moderate confidence

A missing authorization check in SAP NetWeaver Application Server ABAP and S/4HANA allows authenticated attackers to access a specific transaction code and modify text data, creating a high-integrity impact without affecting confidentiality or availability.

MitigationImplement proper authorization checks on the affected transaction code by defining and assigning appropriate authorization objects and roles to restrict access to authorized users only.

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
Sap BasisApplication
Affected:= 700= 701= 702= 731= 740= 750= 751= 752= 753= 754= 755= 756

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
Unchanged
Confidentiality
None
Integrity
High
Availability
None

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

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 SAP NetWeaver AS ABAP or S/4HANA installation
    Query system information or check SAP system profile for component type. On SAP system, run transaction SM51 or check the system version via SAP MMC or transaction OS06 for host information.
    Affected if SAP NetWeaver Application Server ABAP or S/4HANA is installed and running
  2. Determine SAP Basis version
    Execute transaction SM37 or check via SAPMMC console. Alternatively, access SAP system and run transaction code: /n/iwfnd/maint_service for system version, or check SAP Note on kernel version. Use transaction: SYST to view system info or transaction: SLICENSE for license info which includes version.
    Affected if Version matches 700, 701, 702, 731, 740, 750, 751, 752, 753, 754, 755, or 756
  3. Locate the affected transaction code
    Review SAP system transaction code access logs. The vulnerability affects a specific transaction code used for text data modification. Use transaction code: SE93 to view available transaction codes, or check ST03N for transaction usage statistics to identify the specific code mentioned in CVE documentation.
    Affected if The specific vulnerable transaction code is accessible in the system
  4. Verify authorization configuration for the transaction code
    Execute transaction code: SU53 immediately after attempting the affected transaction to check authorization failures. Also use transaction: SUIM to search for authorization objects, and check role assignments via transaction: PFCG.
    Affected if Users without proper authorization objects can still access and execute the transaction code to modify text data
  5. Check user role assignments
    Use transaction: SU01 to view user master records, or transaction: AGR_TCODE_ALL to see which roles have access to which transaction codes. Verify if unrestricted roles are assigned to users.
    Affected if Users possess roles that grant access to the vulnerable transaction without proper authorization object checks

A user is affected if they run SAP NetWeaver AS ABAP or S/4HANA with a Basis version matching 700-756 and the vulnerable transaction code is accessible without proper authorization validation.

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

Implement proper authorization checks on the affected transaction code by defining and assigning appropriate authorization objects and roles to restrict access to authorized users only.

Fix this in Sap Basis Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-0484 — 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-0484 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