← Back
CVE-2025-54802
Path Traversal in pyload-ng (CVE-2025-54802)
Summary
path traversal in pyload-ng (CVE-2025-54802). Successful exploitation can lead to full system takeover. Exploitable via `POST /addcrypted`. Mitigation: upgrade to `0.5.0b3.dev90` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2025-54802** has been found in pyload-ng.
Attackers can target a specific entry point like `POST /addcrypted` over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: ?/10.
What to do: upgrade pyload-ng to **0.5.0b3.dev90** or later.
If unsure, ask your IT team or search "pyload-ng CVE-2025-54802" on the vendor's site.
CVE-2025-54802 (pyload-ng) — CWE-22 /
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: POST /addcrypted / `package` / `addcrypted`
Patched: `0.5.0b3.dev90` — 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
**Path traversal** (CWE-22) exists in pyload-ng. Attackers reach the vulnerable code path via `POST /addcrypted` without authentication.
📍 Affected scope
pyload-ng — . Attack surface: POST /addcrypted / `package` / `addcrypted`.
🔥 Severity
Severity: ?. Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **0.5.0b3.dev90**.
🛡️ 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 `POST /addcrypted` requests with malformed payloads or SQL meta-characters. Run `grep -r 'pyload-ng' .` 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 'pyload-ng' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `pyload-ng` を grep し、稼働しているサービス・バージョンを把握する。
-
3Hunt for indicators of compromise detect
grep 'POST /addcrypted' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで `POST /addcrypted` への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。
-
6Apply patch patch
Upgrade pyload-ng to 0.5.0b3.dev90ステージング環境で 0.5.0b3.dev90 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Replay attack against POST /addcrypted on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
pyload-ng
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.5.0b3.dev90"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2025-54802
- package https://github.com/pyload/pyload
- web https://github.com/pyload/pyload/security/advisories/GHSA-48rp-jc79-2264
- web https://github.com/pyload/pyload/pull/4596
- web https://github.com/pyload/pyload/commit/70a44fe02c03bce92337b5d370d2a45caa4de3d4