CVE-2020-6367
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 · uneditedThere is a reflected cross site scripting vulnerability in SAP NetWeaver Composite Application Framework, versions - 7.20, 7.30, 7.31, 7.40, 7.50. An unauthenticated attacker can trick an unsuspecting authenticated user to click on a malicious link. The end users browser has no way to know that the script should not be trusted, and will execute the script, resulting in sensitive information being disclosed or modified.
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 confidenceReflected cross-site scripting (XSS) vulnerability in SAP NetWeaver Composite Application Framework versions 7.20 through 7.50. An unauthenticated attacker can craft a malicious URL containing JavaScript payload that, when clicked by an authenticated user, executes in the victim's browser context, potentially leading to session hijacking, credential theft, or sensitive data exposure.
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.20= 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
- 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 CAF versionUse SAP transaction code SM51 or transaction code CAFM (if available) to display the Composite Application Framework version information. Alternatively, check the SAP system information via system reports or the SAP NetWeaver Administrator (NWA) console.Affected if The reported version matches 7.20, 7.30, 7.31, 7.40, or 7.50.
-
Verify CAF web component is enabledCheck if the SAP NetWeaver CAF web interface or related ICF (Internet Communication Framework) services are active. Use transaction code SICF to inspect the CAF-related service paths and confirm they are active and not deactivated.Affected if The CAF web services are active and accessible via HTTP/HTTPS.
-
Confirm external exposure of CAF URLsReview web dispatcher or ICM (Internet Communication Manager) configuration to determine if CAF endpoints are exposed to untrusted networks. Check URL patterns that include /sap/bc/caf/ paths in your web server logs or configuration.Affected if CAF URLs are reachable from outside the trusted internal network without additional authentication layers.
-
Inspect for lack of input validationReview any custom CAF applications or configurations that handle URL parameters. Check if parameter handling code implements output encoding or input validation for user-supplied data.Affected if No input validation or output encoding is found for parameters in CAF components.
A user is affected if their SAP NetWeaver CAF version is 7.20 through 7.50 and the CAF web component is accessible, as the reflected XSS can be triggered via a malicious crafted URL.
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-6367. Implement output encoding and input validation for all user-supplied parameters in the affected NetWeaver CAF components. Consider implementing Content Security Policy (CSP) headers as defense-in-depth measure.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-6367 — 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-6367 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