CVE-2020-6272
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 · uneditedSAP Commerce Cloud versions - 1808, 1811, 1905, 2005, does not sufficiently encode user inputs, which allows an authenticated and authorized content manager to inject malicious script into several web CMS components. These can be saved and later triggered, if an affected web page is visited, resulting in Cross-Site Scripting (XSS) vulnerability.
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 confidenceSAP Commerce Cloud versions 1808, 1811, 1905, and 2005 contain a stored Cross-Site Scripting (XSS) vulnerability in web CMS components due to insufficient input encoding. An authenticated content manager can inject malicious JavaScript into CMS components, which persists and executes when other users visit affected web pages.
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= 1808= 1811= 1905= 2005CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Identify SAP Commerce Cloud versionCheck the installed version of SAP Commerce Cloud in the system. This can typically be found in the system information page, version manifest, or by querying the platform configuration (look in the hybris platform properties or admin console).Affected if The installed version matches 1808, 1811, 1905, or 2005 exactly.
-
Determine if CMS module is enabledVerify whether the SAP Commerce Cloud CMS (Content Management System) module is active. Check the hybris administration console or platform configuration for CMS extension status, or look for the presence of CMS-related tables in the database.Affected if The CMS module is installed and active in the environment.
-
Check for content manager user accountsReview user accounts to identify any with content manager or CMS editor roles. These are the roles that can create or modify CMS components where malicious script could be injected.Affected if Content manager or CMS editor user accounts exist in the system.
-
Inspect CMS component content for suspicious entriesExamine stored CMS components in the database or through the backoffice/admin interface for any unexpected script tags, javascript: URIs, or HTML event handlers (such as onload, onerror, onclick) in text fields.Affected if Any CMS component contains unencoded script tags, javascript: protocols, or HTML event handler attributes in user-controllable fields.
The environment is affected if SAP Commerce Cloud version 1808, 1811, 1905, or 2005 is running AND the CMS module is enabled, allowing authenticated content managers to inject persistent malicious scripts into CMS components.
Generated from the published advisory. Verify against your own configuration.
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 dataApply the relevant SAP security patch for CVE-2020-6272 and ensure all user-supplied content in CMS components is properly encoded before rendering. Implement output encoding appropriate for the HTML context.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
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 locallyCheck whether your project pulls in CVE-2020-6272 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-6272 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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