CVE-2024-40624criticalCWE-502

CVE-2024-40624: critical vulnerability in torrentpier

Deserialization of untrusted data in torrentpier/torrentpier

Published · Updated

Follow this CVE+ Monitor torrentpier+ Monitor torrentpier/torrentpier

E-mail alert when it lands in KEV, gets a public PoC or its score goes up.

28Vexday Risk Score

No sign of exploitation. No public exploitation artifact known so far.

ssvc Trackcvss 9.8epss 1.0%
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 workarounds for this vulnerability.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Affected products
torrentpier · torrentpier
Related CVEs — torrentpier

In the same product, most dangerous first.

CVE-2025-64519HIGHTorrentPier is Vulnerable to Authenticated SQL Injection through Moderator Control Panel's topic_id parameterEPSS 0.5%