dbcve.org
Business Planning And ConsolidationApplication · Sap

CVE-2020-6368

MEDIUM · 5.4 CVSS v3.1 Published 2020-10-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
SAP Business Planning and Consolidation, versions - 750, 751, 752, 753, 754, 755, 810, 100, 200, can be abused by an attacker, allowing them to modify displayed application content without authorization, and to potentially obtain authentication information from other legitimate users, leading to 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 confidence

Cross-site scripting (XSS) vulnerability in SAP Business Planning and Consolidation allows authenticated or unauthenticated attackers to inject malicious scripts into application content, potentially hijacking session cookies and authentication credentials from legitimate users viewing the compromised content.

MitigationApply the relevant SAP security patch for CVE-2020-6368 and implement output encoding/validation on user-supplied input fields to prevent script injection.

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
Business Planning And ConsolidationApplication
Affected:= 100= 200= 750= 751= 752= 753= 754= 755= 810

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed SAP BPC version
    Access SAP system information through transaction code SM37 or check the SAP Business Planning and Consolidation system information page in the SAP NetWeaver Administration console. Query the product version using SAP transaction code SXMB_MONI or check the SAP Solution Manager system diagnostics.
    Affected if The installed version matches any of these: 100, 200, 750, 751, 752, 753, 754, 755, or 810.
  2. Verify user input acceptance points
    Review SAP BPC web interfaces and forms where user-supplied data can be submitted to the application. This includes data entry screens for planning models, consolidation worksheets, and reporting interfaces accessible via the SAP BPC web client.
    Affected if User input fields exist in the SAP BPC interface that process and display content without visible server-side output encoding.
  3. Check for authenticated access to BPC web client
    Determine whether the SAP BPC web client is accessible. Attempt to access the BPC logon page through the SAP NetWeaver Portal or direct BPC URL. Verify if anonymous or unauthenticated access is permitted to any BPC content areas.
    Affected if The BPC web client is accessible and processes user input in any form without requiring authentication, or processes input from authenticated sessions.
  4. Inspect application response headers
    Use browser developer tools or a web proxy to capture responses from SAP BPC pages. Examine HTTP response headers and page content for proper Content-Type declarations and absence of security-related headers like X-XSS-Protection or Content-Security-Policy.
    Affected if Responses show missing or weak security headers and rendered content appears to include raw user input without encoding.

Your environment is affected if the installed SAP Business Planning and Consolidation version matches 100, 200, or any version from 750 through 810, and the application processes user-supplied input that renders unencoded in browser content.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the relevant SAP security patch for CVE-2020-6368 and implement output encoding/validation on user-supplied input fields to prevent script injection.

Fix this in Business Planning And Consolidation Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-6368 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-6368 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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