CVE-2020-26835
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, versions - 740, 750, 751, 752, 753, 754 , does not sufficiently encode URL which allows an attacker to input malicious java script in the URL which could be executed in the browser resulting in Reflected Cross-Site Scripting (XSS) vulnerability.
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 confidenceSAP NetWeaver AS ABAP versions 740-754 contain a reflected XSS vulnerability due to insufficient URL encoding. Attackers can inject malicious JavaScript into URLs that execute in victim browsers when they click crafted links.
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= 740= 750= 751= 752= 753= 754CVSS 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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed SAP NetWeaver ABAP versionExecute transaction SM51 or use report SAPCUA_GET_VERSION to retrieve the SAP NetWeaver AS ABAP kernel version. Alternatively, check the sapinfo command output or the system profile parameters (transaction SM37).Affected if The installed version matches 740, 750, 751, 752, 753, or 754 exactly.
-
Locate ABAP applications handling URL parametersReview custom ABAP programs and standard transactions that accept user input via URL parameters (such as programs using parameters or selection screens with URL parameter binding). Use transaction SE80 or ST03 to identify programs that process incoming URL parameters.Affected if ABAP applications accept and process URL parameters without applying output encoding.
-
Inspect ABAP code for insufficient URL encodingSearch ABAP repository (transaction CODE_SCANNER or RS_ABAP_SOURCE_SCAN) for keywords such as CL_HTTP_UTILITY, CL_HTMLB_MANAGER, or direct CL_ABAP_CONV_CODEPAGE usage in programs that output URL parameter values. Examine whether WRITE statements, HTMLB rendering, or Web Dynpro components encode output.Affected if Code outputs URL parameter values directly to HTML responses without using appropriate encoding methods like HTML_ESCAPE or CL_ABAP_CODEPAGE.
-
Verify web exposure of ABAP transactionsCheck SAP ICM (Internet Communication Manager) and Web Dispatcher configuration (transaction SMICM) to determine which ABAP transactions and programs are accessible via HTTP/HTTPS URLs.Affected if ABAP transactions or programs handling URL parameters are exposed via HTTP and reachable by external users.
You are affected if your SAP NetWeaver AS ABAP version is exactly 740, 750, 751, 752, 753, or 754 AND you have ABAP applications that process URL parameters and render them in web pages without proper encoding.
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 SAP security notes/patches for CVE-2020-26835 to implement proper output encoding for URL parameters in the affected ABAP applications.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-26835 — 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-26835 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