CVE-2020-6284
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 (Knowledge Management), versions - 7.30, 7.31, 7.40, 7.50, allows the automatic execution of script content in a stored file due to inadequate filtering with the accessing user's privileges. If the accessing user has administrative privileges, then the execution of the script content could result in complete compromise of system confidentiality, integrity and availability, leading to Stored 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 · moderate confidenceStored Cross-Site Scripting vulnerability in SAP NetWeaver Knowledge Management versions 7.30-7.50. The component fails to properly filter script content in stored files, allowing malicious scripts to execute automatically when users access the contaminated files. Execution occurs with the privileges of the accessing user, and if that user has administrative rights, the attacker could achieve full system compromise.
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= 7.30= 7.31= 7.40= 7.50CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/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 installed SAP NetWeaver versionUse SAP transaction SM51 to display the SAP System Version, or check the kernel version via sapkernel version command. Cross-reference with SAP NetWeaver 7.30, 7.31, 7.40, or 7.50.Affected if Installed version matches 7.30, 7.31, 7.40, or 7.50
-
Verify Knowledge Management component is activeCheck if Knowledge Management services are running via SAP transaction SICF. Look for KM-related services under /sap/bc/kin or search for knowledge management activation.Affected if KM services are active and accessible in the system
-
Confirm Knowledge Management file upload capabilityVerify if users can store files in Knowledge Management repositories via transaction DKMC or check KM configuration in SAP NetWeaver Administrator.Affected if Users have ability to upload and store files in KM repositories
-
Review Knowledge Management access permissionsCheck user roles and authorizations for KM functionality using transaction PFCG. Look for roles containing KM-related authorization objects or Knowledge Management specific permissions.Affected if Non-administrative users have access to upload or modify files in Knowledge Management
Environment is affected if SAP NetWeaver version is 7.30-7.50 and Knowledge Management component is enabled with file storage capabilities accessible to users.
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.
dbcve · scopedApply SAP Security Notes addressing this vulnerability (check SAP Support Portal for CVE-2020-6284 related patches). Until patched, restrict access to Knowledge Management functions to trusted administrators only and implement output encoding for KM file content.
SAP NetWeaver Knowledge Management 7.50 with latest SAP Security Note applied, or migrate to newer NetWeaver stack with fixes
- Check SAP Security Notes for CVE-2020-6284 to obtain the specific patch or correction instruction
- Apply the relevant SAP Security Note (typically available via SAP Support Portal)
- After patching, verify the Knowledge Management component no longer accepts unsanitized script content in stored files
- Test that stored files with potential script payloads are properly encoded/escaped when rendered
- Confirm administrative users cannot trigger automatic script execution via stored files
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-6284 — 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-6284 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