CVE-2016-6858
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 Employee feature in Hybris Management Console (HMC) in SAP Hybris before 5.0.4.11, 5.1.0.x before 5.1.0.11, 5.1.1.x before 5.1.1.12, 5.2.0.x and 5.3.0.x before 5.3.0.10, 5.4.x before 5.4.0.9, 5.5.0.x before 5.5.0.9, 5.5.1.x before 5.5.1.10, 5.6.x before 5.6.0.8, and 5.7.x before 5.7.0.9 allows remote authenticated users to inject arbitrary web script or HTML via the Name 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 confidenceStored XSS vulnerability in the Create Employee feature of Hybris Management Console (HMC) where the Name field does not properly sanitize user input, allowing authenticated users to inject arbitrary HTML or JavaScript that executes when the data is rendered.
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.0.4, < 5.0.4.11>= 5.1.0, < 5.1.0.11>= 5.1.1, < 5.1.1.12>= 5.2.0, < 5.2.0.10>= 5.3.0, < 5.3.0.10>= 5.4.0, < 5.4.0.9>= 5.5.0, < 5.5.0.9>= 5.5.1, < 5.5.1.10>= 5.6.0, < 5.6.0.8>= 5.7.0, < 5.7.0.9CVSS 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 Hybris versionLocate the hybris version file (typically in <hybris_home>/hybris/bin/platform/build.number or check the Hybris Administration Console for version info)Affected if The installed version falls within any of these ranges: >=5.0.4 to <5.0.4.11, >=5.1.0 to <5.1.0.11, >=5.1.1 to <5.1.1.12, >=5.2.0 to <5.2.0.10, >=5.3.0 to <5.3.0.10, >=5.4.0 to <5.4.0.9, >=5.5.0 to <5.5.0.9, >=5.5.1 to <5.5.1.10, >=5.6.0 to <5.6.0.8, or >=5.7.0 to <5.7.0.9
-
Confirm HMC is enabledAccess the Hybris Management Console URL (typically /hybris/console or /hmc) and verify it is reachable and not disabled in configurationAffected if HMC is accessible and the version is within the affected ranges listed above
-
Check Create Employee accessLog into HMC and navigate to the Create Employee feature (usually under User Management or similar section) to confirm the feature exists and is accessible to your user roleAffected if You can access the Create Employee form in HMC and your Hybris version is in the affected ranges
-
Verify input handlingIn the Create Employee form, inspect the Name field to confirm it accepts user input without visible sanitization or encodingAffected if The Name field accepts plain text input and your environment meets the version and access conditions above
You are affected if your Hybris version is within any of the affected ranges AND the HMC Create Employee feature is 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.0.4.115.1.0.115.1.1.12
Apply vendor patches for affected versions (5.0.4.11, 5.1.0.11, 5.1.1.12, 5.3.0.10, 5.4.0.9, 5.5.0.9, 5.5.1.10, 5.6.0.8, 5.7.0.9 and later). Implement proper input validation and output encoding on the Name field.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-6858 — 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-6858 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