Skip to content
Fencer Vulns
critical 9.8

CVE-2023-30801 json

qBittorrent Web UI Default Credentials Lead to RCE

published 2023-10-10 3 y ago modified 2026-06-17 4 mo ago also EUVD-2023-35161

cvss
9.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.2%
EPSS 1.2% chance of exploitation in 30 days, percentile 69%
public exploits
0
none known

Summary

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.

Patch / fix

  • qbittorrent Package Hub 15 SP5, Package Hub 15 SP4, openSUSE Leap 15.5 +1 more 4.6.2-bp155.2.3.1
  • libtorrent-rasterbar Package Hub 15 SP5, Package Hub 15 SP4, openSUSE Leap 15.5 +1 more 2.0.9-bp155.2.3.1

opensuse advisories openSUSE-SU-2023:0391-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2023-30801 updated cvss 9.8

qbittorrent: default credentials allowed by default

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.24% chance of exploitation in the next 30 days, higher than 69% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

  • qBittorrent qBittorrent client

Classification

Weakness
  • CWE-1392 Use of Default Credentials
  • CWE-798 Use of Hard-coded Credentials

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.