dbcve.org
Netweaver Application Server AbapApplication · Sap

CVE-2020-26818

HIGH · 8.8 CVSS v3.1 Published 2020-11-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/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
SAP NetWeaver AS ABAP (Web Dynpro), versions - 731, 740, 750, 751, 752, 753, 754, 755, 782, allows an authenticated user to access Web Dynpro components, which reveals sensitive system information that would otherwise be restricted to highly privileged users because of missing authorization, resulting in Information Disclosure.

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

Authenticated users can access Web Dynpro components in SAP NetWeaver AS ABAP (versions 731-782) that expose sensitive system information due to missing authorization checks. This allows regular authenticated users to view data that should be restricted to highly privileged users, resulting in information disclosure.

MitigationApply the relevant SAP security note/patch that implements proper authorization checks on the affected Web Dynpro components. Test the fix in a non-production system before deploying to production to ensure no functionality breaks.

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:= 731= 740= 750= 751= 752= 753= 754= 755= 782

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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 the SAP NetWeaver AS ABAP version
    Execute transaction SM51 or use SAP Management Console to view the kernel release and SP levels. Alternatively, check the SAP system information via the SAP Logon pad or by accessing the system details in transaction SM37.
    Affected if The installed version matches any of the following: 731, 740, 750, 751, 752, 753, 754, 755, or 782.
  2. Determine if Web Dynpro is in use
    Use transaction SE80 to browse the repository and search for Web Dynpro applications (select 'Web Dynpro' from the dropdown). Alternatively, check transaction WD_GLOBAL_CONFIGURATION or query table WDY_APPLICATION for active Web Dynpro components.
    Affected if Web Dynpro applications exist and are accessible within the ABAP system.
  3. Verify the authorization role configuration for Web Dynpro components
    Use transaction PFCG to examine the roles assigned to standard users. Check whether roles contain authorization objects S_WDY_ACTVT or similar Web Dynpro-related authorization objects, and whether the activity field (ACTVT) is properly restricted to administrative actions only.
    Affected if Regular authenticated users have roles that grant access to sensitive Web Dynpro components without proper activity restrictions.
  4. Review the Web Dynpro component authorization settings
    Execute transaction WDY_AUTHORITY_CHECK or inspect the Web Dynpro component configuration via SE80 by selecting a specific Web Dynpro component and checking its 'Authorization' tab or authority-check implementations in the component controller.
    Affected if The Web Dynpro components lack explicit authorization checks in their implementation or configuration, allowing any authenticated user to access privileged data.

A system is affected if it runs SAP NetWeaver AS ABAP versions 731, 740, 750-755, or 782, has Web Dynpro components deployed, and does not enforce proper authorization checks on those components for sensitive data access.

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 the relevant SAP security note/patch that implements proper authorization checks on the affected Web Dynpro components. Test the fix in a non-production system before deploying to production to ensure no functionality breaks.

Fix this in Netweaver Application Server Abap Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing12.0 h
  • Review / QA6.0 h
38.0 hours of engineering $6,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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