CVE-2016-6857
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 · uneditedCross-site scripting (XSS) vulnerability in the Create Catalogue feature in Hybris Management Console (HMC) in SAP Hybris before 5.2.0.13, 5.3.x before 5.3.0.11, 5.4.x before 5.4.0.11, 5.5.0.x before 5.5.0.10, 5.5.1.x before 5.5.1.11, 5.6.x before 5.6.0.11, and 5.7.x before 5.7.0.15 allows remote authenticated users to inject arbitrary web script or HTML via the ID field.
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 confidenceCross-site scripting (XSS) vulnerability in the Create Catalogue feature of SAP Hybris Management Console (HMC). The ID field does not properly sanitize user input, allowing authenticated users to inject arbitrary JavaScript or HTML code that executes in other users' browsers.
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>= 5.2.0, < 5.2.0.13>= 5.3.0, < 5.3.0.11>= 5.4.0, < 5.4.0.11>= 5.5.0, < 5.5.0.10>= 5.5.1, < 5.5.1.11>= 5.6.0, < 5.6.0.11>= 5.7.0, < 5.7.0.15CVSS 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.0/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 installed Hybris versionLocate the version information in your Hybris installation. Check the file 'hybris/bin/platform/build.number' or look in the 'hybris/config/local.properties' for version properties. Alternatively, access the Hybris Administration Console and check the 'About' or 'System Information' section.Affected if The installed version falls within any of these ranges: >= 5.2.0 and < 5.2.0.13; >= 5.3.0 and < 5.3.0.11; >= 5.4.0 and < 5.4.0.11; >= 5.5.0 and < 5.5.0.10; >= 5.5.1 and < 5.5.1.11; >= 5.6.0 and < 5.6.0.11; or >= 5.7.0 and < 5.7.0.15.
-
Verify Hybris Management Console is accessibleAttempt to access the HMC interface by navigating to the HMC URL for your installation (typically /hybris/ or /hmc/). Confirm that you can log in with valid credentials.Affected if HMC is enabled and accessible to authenticated users, and the installed Hybris version is within the affected ranges listed above.
-
Confirm Create Catalogue feature existsLog into HMC and navigate through the navigation tree to locate the Catalogue management section. Look for a 'Create Catalogue' or similar option under the Commerce or Catalogue management area.Affected if The Create Catalogue feature is present and available to authenticated users in an affected Hybris version.
-
Review Catalogue ID input handlingIf you have access to the Hybris configuration or source code, examine how the Catalogue ID field handles user input in the Create Catalogue wizard. Look for lack of input validation or output encoding in the relevant JSP or controller files.Affected if The Catalogue ID field accepts and displays raw user input without proper sanitization or encoding, which is the case for unpatched versions within the affected ranges.
You are affected if your Hybris version is within any of the specified ranges AND the Hybris Management Console with the Create Catalogue feature is enabled and accessible to authenticated users.
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 data5.2.0.135.3.0.115.4.0.11
Apply vendor-provided patches for the affected Hybris versions (5.2.0.13, 5.3.0.11, 5.4.0.11, 5.5.0.10, 5.5.1.11, 5.6.0.11, or 5.7.0.15 and later). Implement output encoding and input validation on the Catalogue ID field.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-6857 — 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-2016-6857 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