Skip to content

Vendor

torrentflux vulnerabilities

13 published CVES affecting torrentflux, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).

Total
13
Critical
0
High
0
Medium
12
Low
1
Unscored
0
CISA KEV
0
Atom feed of torrentflux alerts

Products

Latest torrentflux CVEs

Newest publication first

  1. MediumCVSS 6.0 EPSS 2.0%

    html/index.php in TorrentFlux 2.3 allows remote authenticated users to execute arbitrary code via a URL with a file containing an executable extension in the url_upload parameter, which is downloaded by TorrentFlux and can be accessed via a direct request in a html/downloads/ use...

  2. MediumCVSS 6.5 EPSS 2.7% Public exploit

    Directory traversal vulnerability in viewnfo.php in (1) TorrentFlux before 2.2 and (2) torrentflux-b4rt before 2.1-b4rt-972 allows remote authenticated users to read arbitrary files via .. (dot dot) sequences in the path parameter, a different vector than CVE-2006-6328.

  3. MediumCVSS 6.5 EPSS 2.9% Public exploit

    Directory traversal vulnerability in downloaddetails.php in TorrentFlux 2.2 allows remote authenticated users to read arbitrary files via .. (dot dot) sequences in the alias parameter, a different vector than CVE-2006-6328.

  4. MediumCVSS 6.0 EPSS 1.3%

    metaInfo.php in TorrentFlux 2.2, when $cfg["enable_file_priority"] is false, allows remote attackers to execute arbitrary commands via shell metacharacters (backticks) in the torrent parameter to (1) details.php and (2) startpop.php.

  5. LowCVSS 2.6 EPSS 1.9%

    Multiple cross-site scripting (XSS) vulnerabilities in TorrentFlux 2.1 allow remote attackers to inject arbitrary web script or HTML via the (1) action, (2) file, and (3) users array variables in (a) admin.php, which are not properly handled when the administrator views the Activ...

  6. MediumCVSS 6.8 EPSS 1.7%

    Cross-site scripting (XSS) vulnerability in admin.php in TorrentFlux 2.1 allows remote attackers to inject arbitrary web script or HTML via (1) the $user_agent variable, probably obtained from the User-Agent HTTP header, and possibly (2) the $ip_resolved variable.

Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.