dbcve.org
Tealeaf Customer ExperienceApplication · Ibm

CVE-2016-5975

MEDIUM · 5.4 CVSS v3.0 Published 2016-09-26
Fix available
A fix is available. Upgrade to after 8.7 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Cross-site scripting (XSS) vulnerability in the Web UI in the web portal in IBM Tealeaf Customer Experience before 8.7.1.8847 FP10, 8.8 before 8.8.0.9049 FP9, 9.0.0 and 9.0.1 before 9.0.1.1117 FP5, 9.0.1A before 9.0.1.5108_9.0.1A FP5, 9.0.2 before 9.0.2.1223 FP3, and 9.0.2A before 9.0.2.5224_9.0.2A FP3 allows remote authenticated users to inject arbitrary web script or HTML via an embedded string, a different vulnerability than CVE-2016-5978.

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 confidence

Cross-site scripting (XSS) vulnerability in IBM Tealeaf Customer Experience Web UI allows authenticated remote users to inject arbitrary web script or HTML via an embedded string parameter. The vulnerability affects multiple version branches (8.7.1, 8.8, 9.0.0/9.0.1, 9.0.1A, 9.0.2, 9.0.2A) before specific fix pack updates.

MitigationApply the vendor-supplied fix packs: FP10 for 8.7.1 (8.7.1.8847), FP9 for 8.8 (8.8.0.9049), FP5 for 9.0.1 (9.0.1.1117), and FP3 for 9.0.2/9.0.2A. Input validation and output encoding should also be implemented as defense-in-depth.

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
Tealeaf Customer ExperienceApplication
Affected:<= 8.7= 8.8= 9.0.0= 9.0.1= 9.0.1a= 9.0.2= 9.0.2a

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
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 checks

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

  1. Verify IBM Tealeaf Customer Experience is installed
    Check for Tealeaf installation directories or running services. Common locations include /opt/Tealeaf or C:\Program Files\Tealeaf. Look for tealeaf.exe or tealeaf services in system processes.
    Affected if The software is found on the system and the Web UI component is accessible.
  2. Determine the installed Tealeaf version
    Locate version information in the installation directory. Check for version files, about pages in the admin console, or use the tealeaf command-line version utility if available. The version is typically displayed in the format like 8.7.1, 8.8, 9.0.1, etc.
    Affected if The installed version matches one of: <= 8.7, 8.8, 9.0.0, 9.0.1, 9.0.1a, 9.0.2, or 9.0.2a.
  3. Confirm the Web UI component is enabled
    Verify the Tealeaf Web UI (typically accessed via browser) is accessible. Check the configuration files or services that enable the web interface component.
    Affected if The Web UI is accessible without being restricted by network or authentication controls.
  4. Check installed fix pack level
    Review the fix pack or patch level installed. This is often visible in the admin console about page, in a README file within the installation, or in a specific version/build file. Compare against the fixed versions: 8.7.1.8847 (FP10), 8.8.0.9049 (FP9), 9.0.1.1117 (FP5), or 9.0.2/9.0.2A FP3.
    Affected if The installed fix pack version is lower than the fixed versions listed, or no fix pack is installed.

A user is affected if IBM Tealeaf Customer Experience is installed with a version in the 8.7.1 through 9.0.2A range and the Web UI component is accessible, without the corresponding fix pack (FP10 for 8.7.1, FP9 for 8.8, FP5 for 9.0.1, or FP3 for 9.0.2/9.0.2A) applied.

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
Upgrade available Upgrade to a release after 8.7
Interim mitigation

Apply the vendor-supplied fix packs: FP10 for 8.7.1 (8.7.1.8847), FP9 for 8.8 (8.8.0.9049), FP5 for 9.0.1 (9.0.1.1117), and FP3 for 9.0.2/9.0.2A. Input validation and output encoding should also be implemented as defense-in-depth.

Fix this in Tealeaf Customer Experience Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-5975 — 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-5975 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