# CVE-2024-32880: pyLoad allows upload to arbitrary folder lead to RCE

> An authenticated user can upload a crafted template to an arbitrary folder, leading to remote code execution in pyLoad.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Apr 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-3f7w-p8vr-4v5f, PYSEC-2026-492

## What is CVE-2024-32880?

CVE-2024-32880 is a critical vulnerability in pyload, published on 26 Apr 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

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.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

## Which versions are affected by CVE-2024-32880?

3 open source packages ship an affected version, including pyload-ng. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pyload-ng` | PyPI | All versions to 0.5.0 | None |
| `pyload-ng` | PyPI | All versions to 0.5.0 | None |
| `pyload-ng` | PyPI | All versions to 0.5.0 | None |

Products: Pyload Pyload.

## How do I fix CVE-2024-32880?

No fix has been published for CVE-2024-32880 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-32880 being exploited?

There is no known exploitation of CVE-2024-32880 in the wild and no public exploit code.

## Other vulnerabilities in pyload

- [CVE-2023-0297](https://insights.sbomify.com/CVE-2023-0297/): Code Injection in pyload/pyload (critical 9.8)
- [CVE-2026-33992](https://insights.sbomify.com/CVE-2026-33992/): pyLoad: Server-Side Request Forgery via Download Link Submission Enables Cloud Metadata Exfiltration (critical 9.3)
- [CVE-2024-47821](https://insights.sbomify.com/CVE-2024-47821/): pyLoad vulnerable to remote code execution by download to /.pyload/scripts using /flashgot API (critical 9.1)
- [CVE-2026-41133](https://insights.sbomify.com/CVE-2026-41133/): pyLoad has Stale Session Privilege After Role/Permission Change (Privilege Revocation Bypass) (high 8.8)
- [CVE-2023-47890](https://insights.sbomify.com/CVE-2023-47890/): Download to arbitrary folder can lead to RCE (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-32880 and fix it if it is affected.

What it is: CVE-2024-32880 is a critical vulnerability in pyload, published on 26 Apr 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-32880 in the wild and no public exploit code.

Affected packages and fixed versions:
- pyload-ng (PyPI): affected all versions up to 0.5.0; no fix listed
- pyload-ng (PyPI): affected all versions up to 0.5.0; no fix listed
- pyload-ng (PyPI): affected all versions up to 0.5.0; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-32880/ (Markdown: https://insights.sbomify.com/CVE-2024-32880/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-32880
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-32880
- OSV: https://osv.dev/vulnerability/CVE-2024-32880

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-32880/
Summaries are generated and may contain mistakes; the official description above is the record.