p PatchFirst

PatchFirst · Latest vulnerabilities

torrentpier/torrentpier vulnerabilities

Vulnerabilities published for torrentpier/torrentpier in the last 30 days: 0. Listed in the KEV catalogue: 0.

Filter vulnerabilities
Clear filters

Vulnerabilities: 4

  1. GHSA-h29g-c9cx-c73q

    Not ratedFix available

    torrentpier has PHP Serialize Injections

    ### Summary Hi, there. We've found PHP Serialize Injections in your project “torrentpier". According to the OWASP, it can pose a significant risk: enable an attacker to modify serialized objects in order to inject malicious data into the application code, resulting in code execution or an arbitrary reading of the file on any vulnerable system. ### Details In the attachment you can find a report with the number of vulnerabilities, their types and the vulnerable files. To view the lines of vulnerable code you may scan your project with the "[PHP Secure](https://phpsecure.net/?utm_source=github&utm_term=

    • Update to 2.4.4
    Published Updated
  2. CVE-2025-64519

    High · CVSS 8.8EPSS 0.45%Fix available

    TorrentPier is Vulnerable to Authenticated SQL Injection through Moderator Control Panel's topic_id parameter

    TorrentPier is an open source BitTorrent Public/Private tracker engine, written in php. In versions up to and including 2.8.8, an authenticated SQL injection vulnerability exists in the moderator control panel (`modcp.php`). Users with moderator permissions can exploit this vulnerability by supplying a malicious `topic_id` (`t`) parameter. This allows an authenticated moderator to execute arbitrary SQL queries, leading to the potential disclosure, modification, or deletion of any data in the database. Although it requires moderator privileges, it is still severe. A malicious or compromised moderator account can leverage this vulnerability to

    • Update to 2.8.9
    Published Updated
  3. CVE-2024-40624

    Critical · CVSS 9.8EPSS 1%Fix available

    Deserialization of untrusted data in torrentpier/torrentpier

    TorrentPier is an open source BitTorrent Public/Private tracker engine, written in php. In `torrentpier/library/includes/functions.php`, `get_tracks()` uses the unsafe native PHP serialization format to deserialize user-controlled cookies. One can use phpggc and the chain Guzzle/FW1 to write PHP code to an arbitrary file, and execute commands on the system. For instance, the cookie bb_t will be deserialized when browsing to viewforum.php. This issue has been addressed in commit `ed37e6e52` which is expected to be included in release version 2.4.4. Users are advised to upgrade as soon as the new release is available. There are no known workaro

    • Update to 2.4.4
    Published Updated

Check your server

Check your installed stack and versions against the current vulnerability feeds.

Check your server →