dbcve.org
Emptoris SourcingApplication · Ibm

CVE-2016-8950

MEDIUM · 5.4 CVSS v3.0 Published 2017-07-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
61/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
IBM 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: 118837.

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 confidence

IBM Emptoris Sourcing versions 9.5.x through 10.1.x contains a stored XSS vulnerability in the web interface. An authenticated attacker can embed arbitrary JavaScript code into web pages, which executes in the browsers of other users viewing the affected content, potentially leading to session hijacking or credential theft through a trusted session.

MitigationImplement proper input validation and output encoding for all user-supplied data rendered in the web UI. Additionally, deploy Content Security Policy (CSP) headers to provide defense-in-depth against XSS attacks.

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
Emptoris SourcingApplication
Affected:= 9.5= 9.5.0.1= 9.5.1.1= 9.5.1.2= 9.5.1.3= 10.0.0= 10.0.1= 10.0.2= 10.0.4= 10.1.0= 10.1.1

CVSS 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
None
User interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify IBM Emptoris Sourcing version
    Access the web application admin console or about page. Typically found at /sourcing/secure/about.do or through the system administration settings. Alternatively, check the installation directory for version manifest files.
    Affected if The installed version matches any of: 9.5, 9.5.0.1, 9.5.1.1, 9.5.1.2, 9.5.1.3, 10.0.0, 10.0.1, 10.0.2, 10.0.4, 10.1.0, or 10.1.1
  2. Confirm web interface is enabled
    Verify the IBM Emptoris Sourcing web application is running and accessible. Check if the application server (typically WebSphere) is hosting the sourcing module and responding to HTTP/HTTPS requests.
    Affected if The web interface is exposed and the application is operational with user authentication enabled
  3. Verify user input fields exist in web UI
    Log into the web interface as an authenticated user and navigate to areas where users can submit or edit content that gets stored and displayed back to users, such as sourcing event descriptions, supplier information fields, or document metadata.
    Affected if The application stores user-supplied data and renders it back without sanitization in any web-accessible field
  4. Inspect HTTP responses for lack of encoding
    Use a browser developer tool or HTTP proxy to capture requests and responses. Submit a test payload containing HTML script tags in input fields and observe if the response reflects the raw tags back to the browser.
    Affected if User-supplied content is returned in HTTP responses without proper HTML encoding or sanitization

You are affected if your IBM Emptoris Sourcing version falls within 9.5.x through 10.1.x and the web interface with user input functionality is accessible and operational.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper input validation and output encoding for all user-supplied data rendered in the web UI. Additionally, deploy Content Security Policy (CSP) headers to provide defense-in-depth against XSS attacks.

Fix this in Emptoris Sourcing Scoped from the published advisory
  • Consultation3.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
24.0 hours of engineering $4,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,720.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-8950 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-8950 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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