CVE-2016-8946
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: 118833.
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 9.5.x through 10.1.x contains a stored cross-site scripting (XSS) vulnerability in the Web UI. Attackers can embed arbitrary JavaScript code into the application interface, which executes in the browsers of other users viewing the contaminated content, potentially leading to session credential theft.
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.
-
Confirm IBM Emptoris Sourcing installationLocate the application in your environment. Check for IBM Emptoris Sourcing web application files, typically deployed on IBM WebSphere Application Server or similar Java application servers. Look for 'emptoris' or 'sourcing' in application paths or server configurations.Affected if IBM Emptoris Sourcing is deployed and accessible in your environment
-
Determine installed versionAccess the Web UI login page or application administration console. Look for version information in the footer, about page, or help section. Alternatively, check application configuration files or WAR deployment descriptors for version metadata.Affected if The installed version matches 9.5.x, 10.0.0, 10.0.1, 10.0.2, 10.0.4, 10.1.0, or 10.1.1
-
Verify Web UI is enabled and accessibleConfirm the Web UI component is active by attempting to access the application's web interface via HTTP/HTTPS. Check if the '/sourcing' or similar web endpoints respond.Affected if The Web UI is exposed and users can log in or submit content to the application
-
Inspect user-submitted fields for unsanitized inputReview application logs and database records for user input fields such as supplier names, item descriptions, or comment fields. Examine if HTML, JavaScript, or script tags are stored and rendered without encoding.Affected if User-supplied content in the application database contains unencoded HTML or JavaScript that could execute in other users' browsers
A user is affected if IBM Emptoris Sourcing versions 9.5 through 10.1.1 are deployed with the Web UI enabled and unencoded user input is being rendered in the interface.
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 vendor patch or upgrade to a version beyond 10.1.x. If immediate patching is not feasible, implement output encoding and input validation on all user-supplied fields in the web interface.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-8946 — 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-8946 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