← Back
CVE-2025-64519
SQL Injection in torrentpier/torrentpier (CVE-2025-64519)
Summary
SQL injection in torrentpier/torrentpier (CVE-2025-64519). Risk of unauthorized operations or information disclosure. Exploitable via ``modcp.php``. Mitigation: upgrade to `2.8.9` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2025-64519** has been found in torrentpier/torrentpier.
Attackers can target a specific entry point like ``modcp.php`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade torrentpier/torrentpier to **2.8.9** or later.
If unsure, ask your IT team or search "torrentpier/torrentpier CVE-2025-64519" on the vendor's site.
CVE-2025-64519 (torrentpier/torrentpier) — CWE-89 /
Attack surface: `modcp.php` / `topic_id` / `sqlmap`
Patched: `2.8.9` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**SQL injection** (CWE-89) exists in torrentpier/torrentpier. Attackers reach the vulnerable code path via ``modcp.php`` without authentication.
📍 Affected scope
torrentpier/torrentpier — . Attack surface: `modcp.php` / `topic_id` / `sqlmap`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **2.8.9**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'torrentpier/torrentpier' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'torrentpier/torrentpier' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `torrentpier/torrentpier` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade torrentpier/torrentpier to 2.8.9ステージング環境で 2.8.9 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
composer
torrentpier/torrentpier
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.8.9"}]}]
References
- web https://github.com/torrentpier/torrentpier/security/advisories/GHSA-4rwr-8c3m-55f6
- web https://github.com/torrentpier/torrentpier/commit/6a0f6499d89fa5d6e2afa8ee53802a1ad11ece80
- web https://github.com/torrentpier/torrentpier/releases/tag/v2.8.9
- web https://github.com/advisories/GHSA-4rwr-8c3m-55f6