CVE-2016-6114
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 · uneditedIBM Emptoris Sourcing 9.5.x through 10.1.x is vulnerable to cross-site scripting. This vulnerability allows users to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session. IBM X-Force ID: 118352.
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 confidenceIBM Emptoris Sourcing versions 9.5.x through 10.1.x contains a cross-site scripting (XSS) vulnerability in its Web UI that allows attackers to inject arbitrary JavaScript code, potentially enabling session hijacking and credential theft through trusted user sessions.
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= 9.5= 10.0.0= 10.0.1= 10.0.2= 10.0.4= 10.1.0= 10.1.1CVSS 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 IBM Emptoris Sourcing installationCheck your system for IBM Emptoris Sourcing components - look for the application server hosting the Emptoris web application and confirm the product name in your software inventory or deployed applicationsAffected if IBM Emptoris Sourcing is installed and running
-
Determine the installed versionLocate the version information for your Emptoris Sourcing installation - this is typically accessible through the application's about page, the deployment descriptor, or the installation manifests. Compare your version against the affected list: 9.5, 10.0.0, 10.0.1, 10.0.2, 10.0.4, 10.1.0, 10.1.1Affected if The installed version matches one of the affected versions listed in the CVE
-
Confirm Web UI component is accessibleVerify that the Emptoris Sourcing Web UI interface is accessible to users - check if the web application port/endpoint is exposed and functionalAffected if The Web UI is accessible and operational
-
Inspect input handling in Web UI formsSubmit test input containing HTML/JavaScript characters (such as <script>alert('XSS')</script>) in common Web UI input fields (search boxes, forms, parameters) and observe whether the input is returned unencoded in the responseAffected if User-supplied input is reflected in responses without proper encoding, indicating the XSS vulnerability is present
You are affected if IBM Emptoris Sourcing is installed, the version matches 9.5.x through 10.1.x, and the Web UI reflects user input without encoding.
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 dataImplement robust input validation and output encoding for all user-supplied data in the web interface; consider deploying Content Security Policy headers to restrict script execution.
- 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-6114 — 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-6114 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