# CVE-2025-54307: Path traversal in n/a

> Authenticated attackers can exploit path traversal in file upload endpoints to write arbitrary files, leading to remote code execution.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Dec 2025
- **Updated:** 5 Dec 2025
- **Also known as:** GHSA-7gh5-58ch-ph4v

## What is CVE-2025-54307?

CVE-2025-54307 is a high-severity path traversal vulnerability in n/a, published on 4 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered in the Thermo Fisher Torrent Suite Django application 5.18.1. The /configure/plugins/plugin/upload/zip/ and /configure/newupdates/offline/bundle/upload/ endpoints allow low-privilege users to upload ZIP files to the server. The plupload_file_upload function handles these file uploads and constructs the destination file path by using either the name parameter or the uploaded filename, neither of which is properly sanitized. The file extension is extracted by splitting the filename, and a format string is used to construct the final file path, leaving the destination path vulnerable to path traversal. An authenticated attacker with network connectivity can write arbitrary files to the server, enabling remote code execution after overwriting an executable file. An example is the pdflatex executable, which is executed through subprocess.Popen in the write_report_pdf function after requests to a /report/latex/(\d+).pdf endpoint.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Thermofisher Torrent Suite Software.

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

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

## Is CVE-2025-54307 being exploited?

There is no known exploitation of CVE-2025-54307 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-54305](https://insights.sbomify.com/CVE-2025-54305/): Auth bypass in n/a (high 7.8)
- [CVE-2025-54306](https://insights.sbomify.com/CVE-2025-54306/): Command injection in n/a (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-54307 is a high-severity path traversal vulnerability in n/a, published on 4 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-54307 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-54307/ (Markdown: https://insights.sbomify.com/CVE-2025-54307/index.md)
```

## Sources

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

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