# CVE-2025-54306: Command injection in n/a

> Remote attackers can execute arbitrary commands via unsanitized input in network configuration endpoints, requiring administrative access to the Django application.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Dec 2025
- **Updated:** 5 Dec 2025
- **Also known as:** GHSA-42m6-m7p8-vqwv

## What is CVE-2025-54306?

CVE-2025-54306 is a high-severity command injection vulnerability in n/a, published on 4 Dec 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official 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.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2025-54306?

It affects 1 product.


Products: Thermofisher Torrent Suite Software.

## How do I fix CVE-2025-54306?

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

## Is CVE-2025-54306 being exploited?

There is no known exploitation of CVE-2025-54306 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2025-54303](https://insights.sbomify.com/CVE-2025-54303/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2025-54307](https://insights.sbomify.com/CVE-2025-54307/): Path traversal in n/a (high 8.8)
- [CVE-2025-54305](https://insights.sbomify.com/CVE-2025-54305/): Auth bypass in n/a (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-54306 and fix it if it is affected.

What it is: CVE-2025-54306 is a high-severity command injection vulnerability in n/a, published on 4 Dec 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-54306 in the wild and no public exploit code.

Affected product: n/a. 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-2025-54306/ (Markdown: https://insights.sbomify.com/CVE-2025-54306/index.md)
```

## Sources

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

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