# CVE-2022-41558: TIBCO Spotfire Stored Cross Site Scripting (XSS) Vulnerability

> A low-privileged attacker can inject malicious scripts into TIBCO Spotfire visualizations, potentially executing code or stealing data when other users view the content.

- **Severity:** Critical 9.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 15 Nov 2022
- **Updated:** 29 Apr 2025
- **Also known as:** GHSA-f97f-pq83-h6fq

## What is CVE-2022-41558?

CVE-2022-41558 is a critical cross-site scripting vulnerability in TIBCO Spotfire Analyst, published on 15 Nov 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

The Visualizations component of TIBCO Software Inc.'s TIBCO Spotfire Analyst, TIBCO Spotfire Analyst, TIBCO Spotfire Analyst, TIBCO Spotfire Analytics Platform for AWS Marketplace, TIBCO Spotfire Desktop, TIBCO Spotfire Desktop, TIBCO Spotfire Desktop, TIBCO Spotfire Server, TIBCO Spotfire Server, and TIBCO Spotfire Server contains an easily exploitable vulnerability that allows a low privileged attacker with network access to execute 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 TIBCO Spotfire Analyst: versions 11.4.4 and below, TIBCO Spotfire Analyst: versions 11.5.0, 11.6.0, 11.7.0, 11.8.0, 12.0.0, and 12.0.1, TIBCO Spotfire Analyst: version 12.1.0, TIBCO Spotfire Analytics Platform for AWS Marketplace: versions 12.1.0 and below, TIBCO Spotfire Desktop: versions 11.4.4 and below, TIBCO Spotfire Desktop: versions 11.5.0, 11.6.0, 11.7.0, 11.8.0, 12.0.0, and 12.0.1, TIBCO Spotfire Desktop: version 12.1.0, TIBCO Spotfire Server: versions 11.4.8 and below, TIBCO Spotfire Server: 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, and 12.0.1, and TIBCO Spotfire Server: version 12.1.0.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2022-41558?

It affects 4 products.


Products: Tibco Spotfire Analyst, Tibco Spotfire Analytics Platform, Tibco Spotfire Desktop, Tibco Spotfire Server.

## How do I fix CVE-2022-41558?

No fix has been published for CVE-2022-41558 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-41558 being exploited?

There is no known exploitation of CVE-2022-41558 in the wild and no public exploit code.

## Other vulnerabilities in TIBCO Spotfire Analyst

- [CVE-2017-3181](https://insights.sbomify.com/CVE-2017-3181/): SQL injection in Spotfire Analyst (critical 9.8)
- [CVE-2018-5435](https://insights.sbomify.com/CVE-2018-5435/): TIBCO Spotfire Product Family Remote Code Execution Vulnerability (critical 9.6)
- [CVE-2025-3115](https://insights.sbomify.com/CVE-2025-3115/): Spotfire Data Function Vulnerability (critical 9.4)
- [CVE-2020-9416](https://insights.sbomify.com/CVE-2020-9416/): TIBCO Spotfire Stored Cross Site Scripting Vulnerability (high 8.2)
- [CVE-2019-17334](https://insights.sbomify.com/CVE-2019-17334/): TIBCO Spotfire Analyst and Desktop Remote Code Execution Via Shared Files (high 7.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-41558 and fix it if it is affected.

What it is: CVE-2022-41558 is a critical cross-site scripting vulnerability in TIBCO Spotfire Analyst, published on 15 Nov 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-41558 in the wild and no public exploit code.

Affected product: TIBCO Spotfire Analyst. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-41558/ (Markdown: https://insights.sbomify.com/CVE-2022-41558/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-41558
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-41558
- OSV: https://osv.dev/vulnerability/CVE-2022-41558

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-41558/
Summaries are generated and may contain mistakes; the official description above is the record.