CVE-2020-26819
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 · uneditedSAP NetWeaver AS ABAP (Web Dynpro), versions - 731, 740, 750, 751, 752, 753, 754, 755, 782, allows an authenticated user to access Web Dynpro components, that allows them to read and delete database logfiles because of Improper Access Control.
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 confidenceThis is an improper access control vulnerability in SAP NetWeaver AS ABAP's Web Dynpro component. An authenticated user with standard privileges can access Web Dynpro components that should be restricted, allowing unauthorized read and delete operations on database logfiles. This represents a privilege escalation/authorization bypass issue where the application's access controls fail to properly restrict sensitive functionality.
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= 731= 740= 750= 751= 752= 753= 754= 755= 782CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify SAP NetWeaver AS ABAP versionExecute transaction SM51 or use the SAP system information to determine the installed SAP NetWeaver Application Server ABAP version. Compare this version against the affected range: 731, 740, 750, 751, 752, 753, 754, 755, or 782.Affected if The installed version matches any of the affected versions: 731, 740, 750, 751, 752, 753, 754, 755, or 782.
-
Confirm Web Dynpro is enabledCheck if Web Dynpro is actively used in the SAP system by reviewing the Web Dynpro configuration via transaction SICF or checking for deployed Web Dynpro applications in the system.Affected if Web Dynpro components are enabled and accessible in the SAP environment.
-
Review Web Dynpro authorization rolesExamine the authorization role configurations for Web Dynpro components that handle database logfile operations. Use transaction PFCG to inspect roles assigned to standard users and verify if overly permissive access exists for logfile-related functions.Affected if Standard authenticated users have roles that grant access to Web Dynpro components performing database logfile read or delete operations.
-
Audit access to database logfile Web Dynpro componentsLog in with a standard (non-privileged) user account and attempt to access Web Dynpro components that manage database logfiles. Document which components are accessible and whether read or delete operations succeed.Affected if A standard authenticated user can access Web Dynpro components that should be restricted and can perform read or delete operations on database logfiles.
A user is affected if their SAP NetWeaver AS ABAP version is one of the affected versions (731, 740, 750-755, 782) AND Web Dynpro is enabled AND standard users can access restricted database logfile components through Web Dynpro.
Generated from the published advisory. Verify against your own configuration.
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 dataApply the relevant SAP security notes/patches for CVE-2020-26819 and review Web Dynpro component authorization roles to ensure proper access restrictions are enforced for database logfile operations.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-26819 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-26819 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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