CVE-2020-6302

What it is

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.

At a glance

Exploitability

Can be exploited over the network without logging in. High risk of data exposure, data tampering, service disruption.

Exploit odds

0.8% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2020-09-09 13:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 03:23 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.8% in the next 30 days (EPSS).
• Severity: 8.1 HIGH (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2020-09-09 13:15 UTC

Last modified

2026-06-17 03:23 UTC

Exploit probability

0.8% · EPSS, next 30 days

Weakness

CWE-384

Record status

Modified

Affected

• Sap Commerce 6.7
• Sap Commerce 1808
• Sap Commerce 1811
• Sap Commerce 1905
• Sap Commerce 2005

Attack profile CVSS 3.1 · 8.1

Attack vector

Network

Complexity

High

Privileges needed

None

User interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2020-6302.md and follow it. Check whether this project is affected by CVE-2020-6302. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge