CVE-2020-6324
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(BSP Test Application sbspext_table), version-700,701,720,730,731,740,750,751,752,753,754,755, allows an unauthenticated attacker to send polluted URL to the victim, when the victim clicks on this URL, the attacker can read, modify the information available in the victim�s browser leading to Reflected Cross Site Scripting.
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 confidenceReflected Cross Site Scripting (XSS) vulnerability in SAP Netweaver AS ABAP BSP Test Application (sbspext_table) allows unauthenticated attackers to inject malicious scripts via polluted URLs. When victims click these crafted links, attackers can execute arbitrary JavaScript in the browser context to steal session data, credentials, or manipulate displayed content.
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= 754= 755CVSS 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 SAP Netweaver AS ABAP versionExecute transaction SM51 or use transaction SAINT to view installed software components and their release versions. Look for 'SAP NetWeaver AS ABAP' in the component list.Affected if The displayed ABAP version matches any of: 700, 701, 702, 730, 731, 740, 750, 751, 752, 753, 754, or 755
-
Verify sbspext_table BSP application existsUse transaction SE80 or SICF to browse BSP applications. Look for application named 'sbspext_table' under the BSP namespace or test packages.Affected if The sbspext_table BSP application is present in the system
-
Check if BSP test application is activatedExecute transaction SICF, navigate to the path for sbspext_table (typically under /sap/bc/bsp or /sap/public/bsp), and verify the service status shows as 'active'.Affected if The sbspext_table service is in active status
-
Test for XSS vulnerability via URL parameterAccess the URL pattern: http://<host>:<port>/sap/bc/bsp/sap/sbspext_table?param=<script>alert(1)</script> (or similar BSP test page URL). Observe if the script payload is reflected unescaped in the response.Affected if The script tags are rendered directly in the browser without encoding, indicating the XSS vulnerability is present
The environment is affected if running a vulnerable ABAP version (700-755) AND the sbspext_table BSP test application exists and is active, making the vulnerable endpoint accessible.
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 patches for CVE-2020-6324; alternatively, disable the sbspext_table BSP test application if not required in production, or implement input validation/sanitization on the affected endpoint.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-6324 — 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-6324 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