CVE-2025-3115: Spotfire Statistics Services · Code Injection
Affects Spotfire Statistics ServicesSource CVE Database V5
Not known to be exploited · CVSS 9.4 Critical.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 52% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:HExploitation evidence
Disclosed: evidence found.
CVE published 9 Apr 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Spotfire Spotfire Statistics Services | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2025-3115, European organizations should immediately implement the following measures: 1) Apply vendor patches as soon as they become available; monitor TIBCO’s advisories closely. 2) Until patches are released, restrict access to Spotfire Statistics Services to trusted networks and users only, using network segmentation and firewall rules. 3) Implement strict input validation and sanitization on all file uploads, ensuring filenames and file contents are checked against a whitelist of allowed patterns and types. 4) Enforce the principle of least privilege for all accounts interacting with Spotfire services, minimizing permissions to only what is necessary. 5) Monitor logs and network traffic for unusual activity related to file uploads or code execution attempts within Spotfire environments. 6) Consider deploying Web Application Firewalls (WAFs) with custom rules to detect and block injection attempts. 7) Conduct security awareness training for administrators and users about the risks of malicious file uploads and suspicious activity. 8) Review and harden the configuration of Spotfire services, disabling unnecessary features that could be exploited. These steps go beyond generic advice by focusing on access control, input validation, and proactive monitoring tailored to the specific vulnerability characteristics.
Description
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