dbcve.org
Spotfire AnalystApplication · Tibco

CVE-2023-26220

MEDIUM · 5.4 CVSS v3.1 Published 2023-10-10
Fix available
A fix is available. Upgrade to after 11.4.11 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
The Spotfire Library component of TIBCO Software Inc.'s Spotfire Analyst and Spotfire Server contains an easily exploitable vulnerability that allows a low privileged attacker with network access to execute a Stored Cross Site Scripting (XSS) on the affected system. A successful attack using this vulnerability requires human interaction from a person other than the attacker. Affected releases are TIBCO Software Inc.'s Spotfire Analyst: versions 11.4.7 and below, versions 11.5.0, 11.6.0, 11.7.0, 11.8.0, 12.0.0, 12.0.1, 12.0.2, 12.0.3, and 12.0.4, versions 12.1.0 and 12.1.1 and Spotfire Server: versions 11.4.11 and below, versions 11.5.0, 11.6.0, 11.6.1, 11.6.2, 11.6.3, 11.7.0, 11.8.0, 11.8.1, 12.0.0, 12.0.1, 12.0.2, 12.0.3, 12.0.4, and 12.0.5, versions 12.1.0 and 12.1.1.

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

Stored Cross-Site Scripting (XSS) vulnerability in the Spotfire Library component allows a low-privileged attacker with network access to inject malicious scripts that execute when other users view the affected library content. The attack requires human interaction from a victim user, typically by viewing or interacting with the compromised library item.

MitigationApply the vendor-provided patch or upgrade to a fixed version of TIBCO Spotfire Analyst and Server. Until then, consider restricting Library access permissions and monitoring for suspicious content.

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
Spotfire AnalystApplication
Affected:<= 11.4.7= 11.5.0= 11.6.0= 11.7.0= 11.8.0= 12.0.0= 12.0.1= 12.0.2= 12.0.3= 12.0.4= 12.1.0= 12.1.1
Spotfire ServerApplication
Affected:<= 11.4.11= 11.5.0= 11.6.0= 11.6.1= 11.6.2= 11.6.3= 11.7.0= 11.8.0= 11.8.1= 12.0.0= 12.0.1= 12.0.2

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.1/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. Identify Spotfire Analyst version
    Open Spotfire Analyst, go to Help > About Spotfire Analyst. The version is displayed in the dialog. Alternatively, check the installed programs list in Windows Control Panel.
    Affected if The version matches any of these: <= 11.4.7, 11.5.0, 11.6.0, 11.7.0, 11.8.0, 12.0.0, 12.0.1, 12.0.2, 12.0.3, 12.0.4, 12.1.0, or 12.1.1
  2. Identify Spotfire Server version
    Log into the Spotfire Server administration console. Navigate to Administration > Diagnostics > Server Information. The version is listed on that page.
    Affected if The version matches any of these: <= 11.4.11, 11.5.0, 11.6.0, 11.6.1, 11.6.2, 11.6.3, 11.7.0, 11.8.0, 11.8.1, 12.0.0, 12.0.1, or 12.0.2
  3. Confirm Library component is accessible
    Log into Spotfire as a standard user. Attempt to access the Library panel (usually the left sidebar in Analyst). Try to add or upload content to any Library folder where you have write access.
    Affected if The Library interface loads and allows content viewing or creation for a low-privileged user account.
  4. Check library permissions for low-privilege users
    In Spotfire Server administration console, go to Library Administration > Permissions. Review which user roles have Create or Modify permissions on library folders.
    Affected if Users with low-privilege roles (non-admin) have Create or Modify permissions on any library folder.

You are affected if your installed Spotfire Analyst or Server version matches the affected list AND the Library component is accessible to users with low privileges who can create or modify library content.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 11.4.11
Interim mitigation

Apply the vendor-provided patch or upgrade to a fixed version of TIBCO Spotfire Analyst and Server. Until then, consider restricting Library access permissions and monitoring for suspicious content.

Recommended fix Moderate confidence

TIBCO Spotfire Analyst and Server version 12.2.0 or later

  1. 1. Identify the currently installed Spotfire Analyst and Spotfire Server versions in your environment.
  2. 2. For Spotfire Analyst: Upgrade to version 12.2.0 or later, as this version includes the fix for the stored XSS vulnerability in the Library component.
  3. 3. For Spotfire Server: Upgrade to version 12.2.0 or later, as this version includes the fix for the stored XSS vulnerability in the Library component.
  4. 4. Verify the upgrade by checking the TIBCO Spotfire release notes for version 12.2.0 to confirm the CVE-2023-26220 fix is included.
  5. 5. After upgrading, test the Spotfire Library functionality to ensure normal operations.
  6. 6. Coordinate the upgrade during a planned maintenance window as the upgrade may require brief service interruption.
Caveat Review TIBCO Spotfire 12.2.0 release notes for any compatibility changes or deprecated features before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Spotfire Analyst Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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