CVE-2020-6246
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 Business Server Pages Test Application SBSPEXT_TABLE, versions 700, 701, 702, 730, 731, 740, 750, 751, 752, 753, 754, does not sufficiently encode user-controlled inputs, 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 Business Server Pages Test Application SBSPEXT_TABLE fails to properly encode user-controlled inputs, allowing attackers to inject malicious scripts via reflected XSS. The vulnerability affects multiple versions (700-754) and requires user interaction (e.g., tricking a user into clicking a crafted link) to exploit.
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= 700= 701= 702= 730= 731= 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 AS ABAP versionQuery the SAP system for the ABAP kernel version using transaction SM51 or by checking the SAP kernel release information. Alternatively, use the SAP ABAP report SYST-VERSION or check the SAP system landscape information.Affected if The installed version matches one of the affected versions: 700, 701, 702, 730, 731, 740, 750, 751, 752, 753, or 754
-
Locate the SBSPEXT_TABLE BSP applicationSearch for the BSP application SBSPEXT_TABLE in the SAP system using transaction SE80 or BSP application browser. The application is located in the BSP repository under the namespace related to test/seed applications.Affected if The SBSPEXT_TABLE BSP application exists in the system
-
Verify BSP application is accessibleAttempt to access the BSP application URL pattern: /sap/bc/bsp/sap/sbspext_table or verify through transaction SICF that the BSP service is active. Check if the test application is exposed via the HTTP handler.Affected if The SBSPEXT_TABLE BSP application is active and reachable via HTTP/HTTPS endpoints
-
Confirm application is in production useReview whether the system is a production system and whether test applications like SBSPEXT_TABLE are intended to be disabled in this environment. Check system usage type and security configuration.Affected if The system is a production environment where test applications should be restricted but SBSPEXT_TABLE remains accessible
A user is affected if their SAP NetWeaver AS ABAP version matches 700, 701, 702, 730, 731, 740, 750, 751, 752, 753, or 754 AND the SBSPEXT_TABLE BSP test application is present and accessible in their environment.
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 available SAP security patches for this vulnerability. As a compensating control, disable or restrict access to the SBSPEXT_TABLE test application in production environments, and implement output encoding for any user-supplied data displayed in BSP pages.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.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 $4,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-6246 — 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-6246 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