dbcve.org
Spotfire Enterprise Runtime For RApplication · Tibco

CVE-2025-3115

CRITICAL · 9.8 CVSS v3.1 Published 2025-04-09
Fix available
A fix is available. Upgrade to 1.17.7 / 6.1.5 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
Injection Vulnerabilities: Attackers can inject malicious code, potentially gaining control over the system executing these functions. Additionally, insufficient validation of filenames during file uploads can enable attackers to upload and execute malicious files, leading to arbitrary code execution

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

CVE-2025-3115 is a critical injection vulnerability combined with insufficient filename validation in file upload functionality. Attackers can inject malicious code through input fields and upload files with crafted filenames that can be executed on the server, leading to arbitrary code execution and potential system compromise.

MitigationImplement strict input validation and sanitization for all user-supplied data, particularly focusing on filename validation for file uploads including extension allowlisting, content-type verification, and storing uploaded files outside the web root or in non-executable storage.

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 Enterprise Runtime For RApplication
Affected:< 6.1.5< 1.17.7= 1.18.0= 1.19.0= 1.20.0= 1.21.0= 1.21.1
Spotfire Statistics ServicesApplication
Affected:< 14.0.7= 14.1.0= 14.2.0= 14.3.0= 14.4.0= 14.4.1
Spotfire AnalystApplication
Affected:< 14.0.6= 14.1.0= 14.2.0= 14.3.0= 14.4.0= 14.4.1
Spotfire Deployment KitApplication
Affected:< 14.0.7= 14.1.0= 14.2.0= 14.3.0= 14.4.0= 14.4.1
Spotfire DesktopApplication
Affected:< 14.4.2
Spotfire Analytics PlatformApplication
Affected:< 14.4.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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 the installed Tibco Spotfire product
    Locate the Tibco Spotfire installation directory and check for product-specific files such as spotfire.exe, TIB_spottest.exe, or check the program name in Add/Remove Programs (Windows) or installed packages (Linux)
    Affected if The product is one of: Spotfire Enterprise Runtime For R, Spotfire Statistics Services, Spotfire Analyst, Spotfire Deployment Kit, Spotfire Desktop, or Spotfire Analytics Platform
  2. Determine the installed version
    Check the product version via: (1) Help > About in the desktop client, (2) The version information in the installation directory (version.txt or similar), (3) The Spotfire Server admin web interface under Server Configuration > General, or (4) Command line: spotfire --version or equivalent binary with --version flag
    Affected if The installed version matches any of the vulnerable versions listed in the CVE (< 6.1.5, < 1.17.7, = 1.18.0, = 1.19.0, = 1.20.0, = 1.21.0, = 1.21.1, < 14.0.7, = 14.1.0, = 14.2.0, = 14.3.0, = 14.4.0, = 14.4.1, < 14.0.6, < 14.4.2)
  3. Verify if the web-based file upload feature is accessible
    Check if the Spotfire web client or Analyst web interface is enabled and network-accessible. Look for the Spotfire Analyst web upload endpoint or the Statistics Services upload interface. Review web server configuration files (web.xml, server.xml) for exposed upload servlets
    Affected if The web application file upload interface is enabled and reachable over the network, as the vulnerability requires the web-facing upload functionality to be exploited

If you are running any of the listed Tibco Spotfire products at a vulnerable version AND the web-based file upload functionality is enabled and accessible, your environment is affected by this CVE.

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 1.17.7 / 6.1.5 / 14.0.6 or later
Fixed in 1.17.76.1.514.0.6
Interim mitigation

Implement strict input validation and sanitization for all user-supplied data, particularly focusing on filename validation for file uploads including extension allowlisting, content-type verification, and storing uploaded files outside the web root or in non-executable storage.

Fix this in Spotfire Enterprise Runtime For R Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
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,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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