# CVE-2025-64519: TorrentPier is Vulnerable to Authenticated SQL Injection through Moderator Control Panel's topic_id parameter

> Authenticated moderators can execute arbitrary SQL queries via the topic_id parameter, allowing them to read, modify, or delete database data.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Nov 2025
- **Updated:** 12 Nov 2025
- **Also known as:** GHSA-4rwr-8c3m-55f6

## What is CVE-2025-64519?

CVE-2025-64519 is a high-severity SQL injection vulnerability in torrentpier, published on 10 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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 read, modify, or delete data. A patch is available at commit 6a0f6499d89fa5d6e2afa8ee53802a1ad11ece80.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2025-64519?

2 open source packages ship an affected version, including torrentpier/torrentpier. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `torrentpier/torrentpier` | Packagist | All versions | 2.8.9 |
| `torrentpier/torrentpier` | Packagist | All versions | 2.8.9 |

Products: Torrentpier Torrentpier.

## How do I fix CVE-2025-64519?

Upgrade torrentpier/torrentpier to 2.8.9 or later.

## Is CVE-2025-64519 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-64519 exists.

## Other vulnerabilities in torrentpier

- [CVE-2024-1651](https://insights.sbomify.com/CVE-2024-1651/): Torrentpier 2.4.1 - RCE (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-64519 and fix it if it is affected.

What it is: CVE-2025-64519 is a high-severity SQL injection vulnerability in torrentpier, published on 10 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-64519 exists.

Affected packages and fixed versions:
- torrentpier/torrentpier (Packagist): affected all versions; fixed in 2.8.9
- torrentpier/torrentpier (Packagist): affected all versions; fixed in 2.8.9

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-64519/ (Markdown: https://insights.sbomify.com/CVE-2025-64519/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-64519
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-64519
- OSV: https://osv.dev/vulnerability/CVE-2025-64519

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-64519/
Summaries are generated and may contain mistakes; the official description above is the record.