Skip to main content
VulnerabilityPublished Updated

CVE-2025-54306: Improper Input Validation

Source CVE Database V5

0

Not known to be exploited · CVSS 7.2 High.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score
7.2High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.8% chance of exploitation in 30 days – higher than 56% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Dec 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

AI-suggested

1. Immediately restrict administrative access to the /admin/network endpoint to trusted personnel only, using strong multi-factor authentication and network segmentation. 2. Apply strict input validation and sanitization on all network configuration parameters before they are passed to subprocess calls or environment variables. 3. Modify the TSsetnoproxy and TSsetproxy scripts to avoid writing user-controlled data directly into environment variables or executing source commands on /etc/environment without validation. 4. Monitor logs for unusual administrative activity or unexpected environment variable changes. 5. Implement application-level logging and alerting for changes to network configurations. 6. Conduct a thorough review of all subprocess calls in the application to ensure no other injection vectors exist. 7. If possible, deploy application-layer firewalls or runtime application self-protection (RASP) solutions to detect and block suspicious command executions. 8. Coordinate with Thermo Fisher for patches or updates addressing this vulnerability and apply them promptly once available. 9. Educate administrators on the risks of this vulnerability and enforce the principle of least privilege. 10. Regularly audit and rotate administrative credentials to reduce risk of credential compromise.

Description

An issue was discovered in the Thermo Fisher Torrent Suite Django application 5.18.1. A remote code execution vulnerability exists in the network configuration functionality, stemming from insufficient input validation when processing network configuration parameters through administrative endpoints. The application allows administrators to modify the server's network configuration through the Django application. This configuration is processed by Bash scripts (TSsetnoproxy and TSsetproxy) that write user-controlled data directly to environment variables without proper sanitization. After updating environment variables, the scripts execute a source command on /etc/environment; if an attacker injects malicious data into environment variables, this command can enable arbitrary command execution. The vulnerability begins with the /admin/network endpoint, which passes user-supplied form data as arguments to subprocess.Popen calls. The user-supplied input is then used to update environment variables in TSsetnoproxy and TSsetproxy, and finally source $environment is executed.

References

Community reviews

Loading reviews…