dbcve.org
Pyload NgApplication · Pyload Ng Project

CVE-2025-54802

CRITICAL · 9.8 CVSS v3.1 Published 2025-08-05
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
pyLoad is the free and open-source Download Manager written in pure Python. In versions 0.5.0b3.dev89 and below, there is an opportunity for path traversal in pyLoad-ng CNL Blueprint via package parameter, allowing Arbitrary File Write which leads to Remote Code Execution (RCE). The addcrypted endpoint in pyload-ng suffers from an unsafe path construction vulnerability, allowing unauthenticated attackers to write arbitrary files outside the designated storage directory. This can be abused to overwrite critical system files, including cron jobs and systemd services, leading to privilege escalation and remote code execution as root. This issue is fixed in version 0.5.0b3.dev90.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

pyLoad versions 0.5.0b3.dev89 and below contain an unsafe path construction vulnerability in the addcrypted endpoint of the CNL Blueprint. Unauthenticated attackers can exploit a path traversal flaw via the package parameter to write arbitrary files outside the designated storage directory, enabling overwrite of critical system files (cron, systemd services) and achieving root-level RCE.

MitigationUpgrade to pyLoad version 0.5.0b3.dev90 or later which contains the patch for the path traversal vulnerability. If immediate upgrading is not feasible, disable or restrict network access to the addcrypted endpoint.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Pyload NgApplication
Affected:= 0.5.0b3.dev89

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify pyLoad installation and version
    Check the installed pyLoad version by examining the package metadata, running 'pyload --version', or inspecting the version file in the pyLoad installation directory. Compare against the affected range: versions 0.5.0b3.dev89 and below.
    Affected if pyLoad version is 0.5.0b3.dev89 or lower (including all 0.5.0b3.dev versions)
  2. Verify CNL Blueprint is enabled
    Inspect the pyLoad configuration to determine if the CNL (Click'N'Load) Blueprint module is enabled. Look for configuration settings related to CNL or Click'N'Load in the main config file.
    Affected if CNL Blueprint is enabled and accessible in the pyLoad configuration
  3. Confirm addcrypted endpoint exposure
    Check network listeners or web server configuration for pyLoad to identify if the addcrypted endpoint is exposed. The endpoint typically resides under the CNL Blueprint path.
    Affected if The addcrypted endpoint is reachable via HTTP/HTTPS without authentication
  4. Review storage directory configuration
    Examine the pyLoad storage configuration to determine the designated storage path. The vulnerability allows writing outside this directory via path traversal in the package parameter.
    Affected if Storage directory is set to a location that, if escaped, could allow overwriting system files with root privileges

You are affected if pyLoad version 0.5.0b3.dev89 or lower is running with the CNL Blueprint and its addcrypted endpoint exposed to the network.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Upgrade to pyLoad version 0.5.0b3.dev90 or later which contains the patch for the path traversal vulnerability. If immediate upgrading is not feasible, disable or restrict network access to the addcrypted endpoint.

Recommended fix High confidence

0.5.0b3.dev90

  1. 1. Check the current installed version of pyLoad-ng (e.g., using pip show pyload or checking the package manager)
  2. 2. Upgrade pyLoad-ng to version 0.5.0b3.dev90 or later by running: pip install --upgrade pyload-ng or the appropriate package manager command
  3. 3. If using a distribution-provided package, wait for the package repository to update to the fixed version or manually install from source
  4. 4. Restart the pyLoad service to ensure the new version is loaded
  5. 5. Verify the upgrade was successful by checking the version number matches 0.5.0b3.dev90 or later

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Pyload Ng Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get the patch applied

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-54802 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-54802 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data