How severe is CVE-2020-6302?

CVE-2020-6302 has a CVSS 3.x base score of 8.1, rated high severity. It is exploitable over network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2020-6302 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (52nd percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2020-6302?

CVE-2020-6302 primarily affects Sap Commerce. In total, 5 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2020-6302?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2020-6302 published?

CVE-2020-6302 was published on 2020-09-09 and last updated on 2026-06-17.

CVE-2020-6302

CVE-2020-6302 is a high-severity vulnerability in Sap Commerce with a CVSS 3.x base score of 8.1. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-384.

Key facts

Severity: High (CVSS 3.x base score 8.1)
CVSS v2: 7.5
EPSS exploit prediction: 1% (52nd percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-384
Affected product: Sap Commerce
Published: 2020-09-09
Last modified: 2026-06-17

Description

SAP Commerce versions 6.7, 1808, 1811, 1905, 2005 contains the jSession ID in the backoffice URL when the application is loaded initially. An attacker can get this session ID via shoulder surfing or man in the middle attack and subsequently get access to admin user accounts, leading to Session Fixation and complete compromise of the confidentiality, integrity and availability of the application.

Frequently asked questions

What is CVE-2020-6302?: SAP Commerce versions 6.7, 1808, 1811, 1905, 2005 contains the jSession ID in the backoffice URL when the application is loaded initially. An attacker can get this session ID via shoulder surfing or man in the middle attack and subsequently get access to admin user accounts, leading to Session Fixation and complete compromise of the confidentiality, integrity and availability of the application.
How severe is CVE-2020-6302?: CVE-2020-6302 has a CVSS 3.x base score of 8.1, rated high severity. It is exploitable over network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2020-6302 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (52nd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2020-6302?: CVE-2020-6302 primarily affects Sap Commerce. In total, 5 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2020-6302?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2020-6302 published?: CVE-2020-6302 was published on 2020-09-09 and last updated on 2026-06-17.

References

Affected products (5)

cpe:2.3:a:sap:commerce:6.7:*:*:*:*:*:*:*
cpe:2.3:a:sap:commerce:1808:*:*:*:*:*:*:*
cpe:2.3:a:sap:commerce:1811:*:*:*:*:*:*:*
cpe:2.3:a:sap:commerce:1905:*:*:*:*:*:*:*
cpe:2.3:a:sap:commerce:2005:*:*:*:*:*:*:*

More vulnerabilities in Sap Commerce

CVE-2021-27602 — Critical (CVSS 9.9): SAP Commerce, versions - 1808, 1811, 1905, 2005, 2011, Backoffice application allows certain authorized users to create…
CVE-2021-21477 — Critical (CVSS 9.9): SAP Commerce Cloud, versions - 1808,1811,1905,2005,2011, enables certain users with required privileges to edit drools…
CVE-2021-42064 — Critical (CVSS 9.8): If configured to use an Oracle database and if a query is created using the flexible search java api with a…
CVE-2020-6265 — Critical (CVSS 9.8): SAP Commerce, versions - 6.7, 1808, 1811, 1905, and SAP Commerce (Data Hub), versions - 6.7, 1808, 1811, 1905, allows…
CVE-2022-41204 — High (CVSS 8.8): An attacker can change the content of an SAP Commerce - versions 1905, 2005, 2105, 2011, 2205, login page through a…
CVE-2021-40502 — High (CVSS 8.8): SAP Commerce - versions 2105.3, 2011.13, 2005.18, 1905.34, does not perform necessary authorization checks for an…

All CVEs affecting Sap Commerce →

Other CWE-384 (Session Fixation) vulnerabilities

CVE-2024-11317 — Critical (CVSS 10.0): Session Fixation vulnerabilities allow an attacker to fix a users session identifier before login providing an…
CVE-2024-38513 — Critical (CVSS 10.0): Fiber is an Express-inspired web framework written in Go A vulnerability present in versions prior to 2.52.5 is a…
CVE-2021-20151 — Critical (CVSS 10.0): Trendnet AC2600 TEW-827DRU version 2.08B01 contains a flaw in the session management for the device. The router's…
CVE-2025-67446 — Critical (CVSS 9.8): Improper Authentication (Authentication Bypass) exists in Neterbit NW-431F Router 20241014-IR03 and before. The router…
CVE-2026-25101 — Critical (CVSS 9.8): Bludit allows user's session identifier to be set before authentication. The value of this session ID stays the same…
CVE-2026-24352 — Critical (CVSS 9.8): PluXml CMS allows a user's session identifier to be set before authentication. The value of this session ID stays the…

Browse all CWE-384 (Session Fixation) vulnerabilities →