# CVE-2018-5435: TIBCO Spotfire Product Family Remote Code Execution Vulnerability

> Remote attackers can execute arbitrary code on TIBCO Spotfire clients and web players, requiring users to upgrade to patched versions.

- **Severity:** Critical 9.6 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 27 Jun 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-3f6h-wmwv-m6rx

## What is CVE-2018-5435?

CVE-2018-5435 is a critical code injection vulnerability in TIBCO Spotfire Analyst, published on 27 Jun 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The TIBCO Spotfire Client and TIBCO Spotfire Web Player Client components of TIBCO Software Inc.'s TIBCO Spotfire Analyst, TIBCO Spotfire Analytics Platform for AWS Marketplace, TIBCO Spotfire Deployment Kit, TIBCO Spotfire Desktop, and TIBCO Spotfire Desktop Language Packs contain multiple vulnerabilities that may allow for remote code execution. Affected releases are TIBCO Software Inc.'s TIBCO Spotfire Analyst: versions up to and including 7.8.0; 7.9.0; 7.9.1; 7.10.0; 7.10.1; 7.11.0; 7.12.0, TIBCO Spotfire Analytics Platform for AWS Marketplace: versions up to and including 7.12.0, TIBCO Spotfire Deployment Kit: versions up to and including 7.8.0; 7.9.0;7.9.1;7.10.0;7.10.1;7.11.0; 7.12.0, TIBCO Spotfire Desktop: versions up to and including 7.8.0; 7.9.0; 7.9.1; 7.10.0; 7.10.1; 7.11.0;7.12.0, TIBCO Spotfire Desktop Language Packs: versions up to and including 7.8.0; 7.9.0; 7.9.1; 7.10.0; 7.10.1; 7.11.0.

## Which versions are affected by CVE-2018-5435?

It affects 5 products.


Products: Tibco Spotfire Analyst, Tibco Spotfire Analytics Platform for Aws, Tibco Spotfire Deployment Kit, Tibco Spotfire Desktop, Tibco Spotfire Desktop Language Packs.

## How do I fix CVE-2018-5435?

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

## Is CVE-2018-5435 being exploited?

There is no known exploitation of CVE-2018-5435 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-2025-3115](https://insights.sbomify.com/CVE-2025-3115/): Spotfire Data Function Vulnerability (critical 9.4)
- [CVE-2022-41558](https://insights.sbomify.com/CVE-2022-41558/): TIBCO Spotfire Stored Cross Site Scripting (XSS) Vulnerability (critical 9.0)
- [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-2018-5435 and fix it if it is affected.

What it is: CVE-2018-5435 is a critical code injection vulnerability in TIBCO Spotfire Analyst, published on 27 Jun 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-5435 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-2018-5435/ (Markdown: https://insights.sbomify.com/CVE-2018-5435/index.md)
```

## Sources

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

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