TorrentPier Deserialization of Untrusted Data vulnerability

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

9.3 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2024-40624: 1.00% estimated exploitation activity in the next 30 days; percentile 62.73 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary In torrentpier/library/includes/functions.php, gettracks() uses the unsafe native PHP serialization format to deserialize user-controlled cookies: https://github.com/torrentpier/torrentpier/blob/84f6c9f4a081d9ffff4c233098758280304bf50f/library/includes/functions.php#L41-L60 PoC 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 bbt will be deserialized when browsing to viewforum.php.

Published by the source

15 Jul 2024, 17:48 UTC

Last modified by the source

13 May 2026, 13:37 UTC

Source last checked

26 Oct 2026, 14:40 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-fg86-4c2r-7wxw

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-40624

Advisory: TorrentPier Deserialization of Untrusted Data vulnerability
IDs: CVE-2024-40624, GHSA-fg86-4c2r-7wxw
Record: https://patchnext.com/advisories/cve-2024-40624 (revision 1, source checked 26 Oct 2026, 14:40 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: torrentpier/torrentpier 2.4.4. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist torrentpier/torrentpier: affected <= 2.4.3; fixed in 2.4.4

## Suggested inspection (read-only)
- Packagist torrentpier/torrentpier: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on torrentpier/torrentpier.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-fg86-4c2r-7wxw (GitHub-reviewed advisory GHSA-fg86-4c2r-7wxw lists affected ranges: Packagist torrentpier/torrentpier >=0 <=2.4.3)

Commands are suggestions: review each one before running it.