dbcve.org
Torrent Suite SoftwareApplication · Thermofisher

CVE-2025-54306

HIGH · 7.2 CVSS v3.1 Published 2025-12-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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
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.

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 · high confidence

Thermo Fisher Torrent Suite Django 5.18.1 contains an RCE in network configuration. The /admin/network endpoint passes unsanitized user input through subprocess.Popen to Bash scripts (TSsetnoproxy/TSsetproxy) that write directly to environment variables, then execute 'source /etc/environment' - allowing injection of malicious data for arbitrary command execution.

MitigationApply vendor patch when available. Until then, restrict administrative access to /admin/network, implement input validation on all network configuration parameters, and sanitize environment variable values before scripting execution.

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
Torrent Suite SoftwareApplication
Affected:= 5.18.1

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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 installed Torrent Suite version
    Locate the Torrent Suite installation directory and check the version file or package metadata. Common locations include /opt/torrent_suite or the application's version indicator in the admin interface.
    Affected if The installed version is exactly 5.18.1 (this specific version is affected)
  2. Verify /admin/network endpoint exists
    Check if the web application exposes the /admin/network URL path. This is the vulnerable endpoint that handles network configuration.
    Affected if The endpoint is present and accessible without additional authentication controls beyond standard admin login
  3. Locate TSsetnoproxy and TSsetproxy scripts
    Search for the bash scripts TSsetnoproxy and TSsetproxy in the Torrent Suite installation directory, typically under the Django application's helpers or scripts subdirectory.
    Affected if These scripts exist and are executable by the web application user
  4. Inspect network configuration module
    Examine the Django view or controller handling /admin/network requests. Look for subprocess.Popen calls that pass user input to the TSsetnoproxy/TSsetproxy scripts.
    Affected if User-supplied input from network configuration forms flows directly to subprocess execution without sanitization
  5. Check script permissions and environment sourcing
    Review the TSsetnoproxy and TSsetproxy scripts for 'source /etc/environment' or '. /etc/environment' commands that would execute environment variable files.
    Affected if The scripts write user input to environment variables and then source /etc/environment, enabling injection

You are affected if running Torrent Suite version 5.18.1 with the /admin/network endpoint accessible and the TSsetnoproxy/TSsetproxy scripts present in the installation.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patch when available. Until then, restrict administrative access to /admin/network, implement input validation on all network configuration parameters, and sanitize environment variable values before scripting execution.

Fix this in Torrent Suite Software Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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