CVE-2020-6185
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 · uneditedUnder certain conditions ABAP Online Community in SAP NetWeaver (SAP_BASIS version 7.40) and SAP S/4HANA (SAP_BASIS versions 7.50, 7.51, 7.52, 7.53, 7.54), allows an authenticated attacker to store a malicious payload which results in Stored Cross Site Scripting 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 confidenceStored Cross-Site Scripting (XSS) vulnerability in ABAP Online Community component of SAP NetWeaver (SAP_BASIS 7.40) and S/4HANA (SAP_BASIS 7.50-7.54). An authenticated attacker can inject malicious JavaScript payloads that persist in the application and execute in browsers of other users viewing the injected 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= 7.40= 7.50= 7.51= 7.52= 7.53= 7.54CVSS 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
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Check SAP_BASIS versionUse transaction code SM37 or execute SAP kernel version check command to determine the installed SAP_BASIS version. Compare against the affected versions: NetWeaver 7.40 or S/4HANA with SAP_BASIS 7.50 through 7.54.Affected if The installed SAP_BASIS version matches exactly 7.40 for NetWeaver or 7.50, 7.51, 7.52, 7.53, or 7.54 for S/4HANA.
-
Verify ABAP Online Community component is activeUse SAP transaction code SICF to check if the ABAP Online Community service (path typically under /sap/bc/abap community or similar) is active in the system.Affected if The ABAP Online Community ICF service is published and accessible in the SAP system.
-
Confirm authentication method for the componentInspect the ICF service configuration for ABAP Online Community in transaction SICF to determine if it permits authenticated access only or allows anonymous users.Affected if The component is configured to accept authenticated users without additional restrictive controls on content submission.
-
Identify user-contributed content areasNavigate to the ABAP Online Community application via SAP GUI or browser and examine where users can submit or post content that would be visible to other users.Affected if The application accepts and displays user-submitted content that persists in the system for other users to view.
A user is affected if they run SAP NetWeaver 7.40 or S/4HANA with SAP_BASIS 7.50-7.54 AND have the ABAP Online Community component enabled with user content submission capabilities accessible to authenticated 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.
From vendor dataApply SAP security patches for CVE-2020-6185. As interim measure, restrict access to ABAP Online Community to trusted authenticated users only.
- Consultation6.0 h
- Implementation12.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 $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-6185 — 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-6185 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