# CVE-2023-30801: qBittorrent Web UI Default Credentials Lead to RCE

> Remote attackers can exploit default Web UI credentials to execute arbitrary OS commands via the external program feature in qBittorrent.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Oct 2023
- **Updated:** 21 Nov 2025
- **Also known as:** DEBIAN-CVE-2023-30801, GHSA-vchq-5hmx-6hmp, UBUNTU-CVE-2023-30801, openSUSE-SU-2023:0391-1, openSUSE-SU-2024:13477-1

## What is CVE-2023-30801?

CVE-2023-30801 is a critical vulnerability in qBittorrent client, published on 10 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

All versions of the qBittorrent client through 4.5.5 use default credentials when the web user interface is enabled. The administrator is not forced to change the default credentials. As of 4.5.5, this issue has not been fixed. A remote attacker can use the default credentials to authenticate and execute arbitrary operating system commands using the "external program" feature in the web user interface. This was reportedly exploited in the wild in March 2023.

Weakness: CWE-798 (Use of Hard-coded Credentials), CWE-1392 (Use of Default Credentials)

## Which versions are affected by CVE-2023-30801?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libtorrent-rasterbar` | SUSE:Package Hub 15 SP4 | All versions | 2.0.9-bp155.2.3.1 |
| `qbittorrent` | SUSE:Package Hub 15 SP4 | All versions | 4.6.2-bp155.2.3.1 |
| `libtorrent-rasterbar` | SUSE:Package Hub 15 SP5 | All versions | 2.0.9-bp155.2.3.1 |
| `qbittorrent` | SUSE:Package Hub 15 SP5 | All versions | 4.6.2-bp155.2.3.1 |
| `libtorrent-rasterbar` | openSUSE:Leap 15.4 | All versions | 2.0.9-bp155.2.3.1 |
| `qbittorrent` | openSUSE:Leap 15.4 | All versions | 4.6.2-bp155.2.3.1 |
| `libtorrent-rasterbar` | openSUSE:Leap 15.5 | All versions | 2.0.9-bp155.2.3.1 |
| `qbittorrent` | openSUSE:Leap 15.5 | All versions | 4.6.2-bp155.2.3.1 |

Products: Qbittorrent Qbittorrent.

## How do I fix CVE-2023-30801?

Change a configuration setting.

## Is CVE-2023-30801 being exploited?

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

## Other vulnerabilities in qBittorrent client

- [CVE-2019-13640](https://insights.sbomify.com/CVE-2019-13640/): Command injection in n/a (critical 9.8)
- [CVE-2024-51774](https://insights.sbomify.com/CVE-2024-51774/): Security feature bypass in n/a (high 8.1)
- [CVE-2017-12778](https://insights.sbomify.com/CVE-2017-12778/): Auth bypass in n/a (high 7.1)
- [CVE-2017-6503](https://insights.sbomify.com/CVE-2017-6503/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2017-6504](https://insights.sbomify.com/CVE-2017-6504/): Other in n/a (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-30801 and fix it if it is affected.

What it is: CVE-2023-30801 is a critical vulnerability in qBittorrent client, published on 10 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-30801 in the wild and no public exploit code.

Affected product: qBittorrent client. 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-2023-30801/ (Markdown: https://insights.sbomify.com/CVE-2023-30801/index.md)
```

## Sources

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

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