# CVE-2025-55295: qBit Manage Path Traversal Vulnerability

> Authenticated attackers can read arbitrary files from the server filesystem via path traversal in the restore_config_from_backup endpoint.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **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:** 19 Aug 2025
- **Updated:** 19 Aug 2025
- **Also known as:** GHSA-vh56-26wq-vvfv

## What is CVE-2025-55295?

CVE-2025-55295 is a medium-severity path traversal vulnerability in StuffAnThings qbit_manage, published on 19 Aug 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

qBit Manage is a tool that helps manage tedious tasks in qBittorrent and automate them. A path traversal vulnerability exists in qbit_manage's web API that allows authenticated users to read arbitrary files from the server filesystem through the restore_config_from_backup endpoint. The vulnerability allows attackers to bypass directory restrictions and read arbitrary files from the server filesystem by manipulating the backup_id parameter with path traversal sequences (e.g., ../). This vulnerability is fixed in 4.5.4.

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

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


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

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

## Is CVE-2025-55295 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-55295 is a medium-severity path traversal vulnerability in StuffAnThings qbit_manage, published on 19 Aug 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-55295 in the wild and no public exploit code.

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

## Sources

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

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