dbcve.org
CommerceApplication · Sap

CVE-2020-6265

CRITICAL · 9.8 CVSS v3.1 Published 2020-06-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 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.

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 confidence

SAP Commerce and SAP Commerce (Data Hub) contain hardcoded credentials embedded in the software that allow unauthenticated attackers to bypass the authentication and authorization mechanisms configured by system administrators, granting unauthorized access to the system.

MitigationOrganizations should apply SAP security patches for this vulnerability immediately, change any default credentials, and review access logs for signs of exploitation while implementing proper credential management practices.

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
CommerceApplication
Affected:= 6.7= 1808= 1811= 1905
Commerce Data HubApplication
Affected:= 6.7= 1808= 1811= 1905

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 installed SAP product
    Locate the SAP Commerce or SAP Commerce Data Hub installation directory and check for the presence of the platform or datahub components
    Affected if Either SAP Commerce or SAP Commerce Data Hub is installed
  2. Determine SAP Commerce version
    Check the version file or properties in the SAP Commerce installation, typically found in the local.properties file or the system information within the admin console
    Affected if The version is 6.7, 1808, 1811, or 1905
  3. Determine SAP Commerce Data Hub version
    Check the version file or properties in the SAP Commerce Data Hub installation directory, usually in version.properties or through the Data Hub administration interface
    Affected if The Data Hub version is 6.7, 1808, 1811, or 1905
  4. Verify default credentials are in use
    Review configuration files and user management settings to determine if any default or hardcoded credentials are active in the system, particularly for administrative accounts
    Affected if Default credentials configured in SAP Commerce or Data Hub match the hardcoded values embedded in affected versions

You are affected if SAP Commerce or SAP Commerce Data Hub version 6.7, 1808, 1811, or 1905 is installed and running with default credentials still enabled.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Organizations should apply SAP security patches for this vulnerability immediately, change any default credentials, and review access logs for signs of exploitation while implementing proper credential management practices.

Recommended fix Moderate confidence

SAP Commerce 1905 or later (contact SAP for latest supported version and specific patch)

  1. 1. Identify all affected SAP Commerce and SAP Commerce Data Hub instances running versions 6.7, 1808, 1811, or 1905
  2. 2. Review system for any usage of default hard-coded credentials that may have been documented or discovered
  3. 3. Change any hard-coded passwords to strong, unique credentials stored securely (e.g., in secure configuration vaults)
  4. 4. Apply latest available SAP Security Notes for the respective version
  5. 5. Verify authentication and authorization mechanisms are functioning correctly after changes
  6. 6. Rotate all credentials that may have been exposed or used as defaults
Caveat When upgrading between major versions of SAP Commerce, custom extensions and integrations may require testing and updates

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Commerce Scoped from the published advisory
  • Consultation12.0 h
  • Implementation24.0 h
  • Testing16.0 h
  • Review / QA8.0 h
60.0 hours of engineering $10,560
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $16,896.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-6265 — 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-6265 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