dbcve.org
Commerce CloudApplication · Sap

CVE-2020-6238

CRITICAL · 9.3 CVSS v3.1 Published 2020-04-14
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.6, 6.7, 1808, 1811, 1905, does not process XML input securely in the Rest API from Servlet xyformsweb, leading to Missing XML Validation. This affects confidentiality and availability (partially) of SAP Commerce.

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

SAP Commerce fails to validate XML input in its REST API from the xyformsweb servlet, allowing potentially malicious XML to be processed without security checks. This missing XML validation could enable XXE (XML External Entity) injection attacks, leading to unauthorized data access and service disruption.

MitigationImplement secure XML parsing by enabling XXE protection in the XML processor, adding schema validation for incoming XML requests, and ensuring the xyformsweb servlet properly validates all XML input before processing.

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
Commerce CloudApplication
Affected:= 6.6= 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
Changed
Confidentiality
High
Integrity
None
Availability
Low

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

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 Commerce version
    Locate the SAP Commerce installation directory and check the version manifest or properties file (such as version.properties in the hybris bin directory or the platform version file). Alternatively, access the SAP Commerce Admin Console and view the system information panel.
    Affected if The installed version matches 6.6, 6.7, 1808, 1811, or 1905 exactly.
  2. Verify xyformsweb servlet is enabled
    Check the SAP Commerce web.xml configuration file (typically in the config directory or the platform web.xml) for the xyformsweb servlet definition and its URL mapping. Confirm whether this servlet is registered and not commented out.
    Affected if The xyformsweb servlet is present and active in the web.xml configuration.
  3. Confirm REST API accepts XML input on xyformsweb endpoint
    Locate the xyformsweb servlet configuration or controller class. Review whether the servlet accepts POST requests with XML content types (such as application/xml or text/xml). Check the request handling code to confirm XML input is processed.
    Affected if The xyformsweb servlet is configured to accept and process XML request bodies.
  4. Inspect XML parser security configuration
    Examine the XML parser configuration used by the xyformsweb servlet or the underlying Spring/web configuration. Look for the XMLInputFactory or DocumentBuilderFactory settings. Check whether features like XMLConstants.ACCESS_EXTERNAL_DTD, XMLConstants.ACCESS_EXTERNAL_SCHEMA, or property XMLConstants.IS_SUPPORTING_EXTERNAL_ENTITIES are explicitly disabled.
    Affected if The XML parser is configured without disabling external entity processing, or no XXE protection features are explicitly set.

You are affected if you run SAP Commerce version 6.6, 6.7, 1808, 1811, or 1905 with the xyformsweb servlet enabled and it processes XML input without explicit XXE protection in the parser configuration.

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

Implement secure XML parsing by enabling XXE protection in the XML processor, adding schema validation for incoming XML requests, and ensuring the xyformsweb servlet properly validates all XML input before processing.

Fix this in Commerce Cloud Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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