Security Digest · Vulnerability record
CVE-2024-32880: pyLoad allows upload to arbitrary folder lead to RCE
pyload is an open-source Download Manager written in pure Python.
CVSS 9.1 Critical EPSS 1.4% · p71
Should you act?
Critical, preconditions apply
Severe if exploited, but exploitation needs conditions that may not apply to you. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.
- No confirmed exploitation. It is not in CISA’s KEV catalog and CISA’s SSVC assessment records no known exploitation. That can change quickly after a public write-up; re-check if you are affected.
- EPSS 1.4%, percentile 71: FIRST’s model estimates a 1.4% chance of exploitation activity in the next 30 days, higher than 71% of all scored CVEs (moderate). EPSS is a probability, not a verdict.
- Needs an account (high (admin)). Exposure depends on who can log in.
- Only applies if your dependency tree includes
pyload-ng(PyPI) <= 0.5.0, no fixed version listed. Check your lockfile, including transitive dependencies.
What it is
pyload is an open-source Download Manager written in pure Python. An authenticated user can change the download folder and upload a crafted template to the specified folder lead to remote code execution. There is no fix available at the time of publication.
From the GitHub advisory
Summary An authenticated user can change the download folder and upload a crafted template to the specified folder lead to remote code execution
Details example version: 0.5 file:src/pyload/webui/app/blueprints/appblueprint.py
So, if we can control file in the path "pyload/webui/app/templates" in latest version and path in "module/web/media/js"(the difference is the older version0.4.20 only renders file with extension name ".js"), the rendertemplate func will works like SSTI(server-side template injection) when render the evil file we control.
in /settings page and the choose option general/general, where we can change the download folder.
Also, we can find the pyLoad install folder in /info page So, we can change the value of Download folder to the template path. Then through /json/addpackage we can upload a crafted template file to RCE.
Weakness type: CWE-434.
Product: pyload-ng (PyPI) · Assigned by: GitHub_M · Published: 2024-04-26
Affected and fixed versions
| Ecosystem | Package | Vulnerable | First fixed |
|---|---|---|---|
| PyPI | pyload-ng | <= 0.5.0 | none listed |
| Vendor | Product | Affected versions (per CVE record) |
|---|---|---|
| pyload | pyload | <= 4.2.0 |
Severity scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| GitHub_M | 3.1 | 9.1 Critical | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H |
| GitHub | 3.1 | 9.1 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H |
- Attack vector: network (remotely reachable)
- Attack complexity: low
- Privileges required: high (admin)
- User interaction: none
- Scope: changed (can affect other components)
CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.
Exploitation and urgency
- CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
- CISA SSVC assessment: exploitation none, automatable no, technical impact total.
- FIRST EPSS (model of 2026-10-21): 1.35% probability of exploitation activity in the next 30 days; percentile 71.
Timeline
- — GitHub-reviewed advisory GHSA-3f7w-p8vr-4v5f published (critical)
- — CVE record published by GitHub_M
- — CVE record last updated
Sources and references
Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.
Vulnerability records
- GitHub Advisory GHSA-3f7w-p8vr-4v5f github.com
- CVE.org record CVE-2024-32880 cve.org
- NVD entry CVE-2024-32880 nvd.nist.gov
Other references from the CVE record and advisory
- github.com github.com