CVE-2020-6323
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 Enterprise Portal (Fiori Framework Page) versions - 7.50, 7.31, 7.40, does not sufficiently encode user-controlled inputs and allows an attacker on a valid session to create an XSS that will be both reflected immediately and also be persisted and returned in further access to the system, resulting in 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 confidenceCross-site scripting (XSS) vulnerability in SAP NetWeaver Enterprise Portal's Fiori Framework Page versions 7.31, 7.40, and 7.50. The application fails to sufficiently encode user-controlled inputs, allowing an authenticated attacker to inject malicious JavaScript that executes both immediately upon submission and persists for future users, affecting any user who accesses 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.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 Enterprise Portal installationLocate the SAP NetWeaver system and determine the product version. Typically found via SAP System GUI transaction SM37, or by checking the SAP start report output, or by querying the SAP system landscape directory (SLD).Affected if The system is running SAP NetWeaver Enterprise Portal version 7.31, 7.40, or 7.50 specifically.
-
Verify Fiori Framework Page component is activeCheck if the Fiori Framework Page (FFP) is deployed and active on the Enterprise Portal. This can be verified through the SAP Portal Catalog in the Administration Console, or by checking the deployed PAR files for Fiori components, or via transaction SE80 looking for Fiori Framework Page related web modules.Affected if Fiori Framework Page component is installed and accessible on the Enterprise Portal.
-
Confirm user access to Fiori launchpad or Fiori-based applicationsDetermine if any user roles grant access to Fiori-based applications or the Fiori launchpad. Check user role assignments via transaction PFCG or the User Administration console in the Enterprise Portal.Affected if Authenticated users have access to Fiori Framework Page functionality where user input can be submitted.
-
Inspect for existing XSS indicators in HTTP traffic or logsReview SAP NetWeaver HTTP access logs (default location: /usr/sap/<SID>/<instance>/log) and Internet Communication Manager (ICM) logs for suspicious script injection patterns in request parameters. Also examine the Portal Runtime logs for any anomalous script tags in user-submitted fields.Affected if Malicious JavaScript or script tags appear in logs associated with Fiori Framework Page requests, indicating active exploitation or attempted injection.
Your environment is affected if SAP NetWeaver Enterprise Portal is running exactly version 7.31, 7.40, or 7.50 AND the Fiori Framework Page component is deployed and 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 the relevant SAP security patch for CVE-2020-6323. Additionally, implement output encoding for all user-controlled data and consider Content Security Policy (CSP) headers as a defense-in-depth measure.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-6323 — 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-6323 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