pyLoad allows upload to arbitrary folder lead to RCE

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

• CVE-2024-32880: 1.35% estimated exploitation activity in the next 30 days; percentile 71.63 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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. PoC First login into the admin page, then visit the info page to get the path of pyload installation folder. Second, change the download folder to…

Published by the source

24 Apr 2024, 21:16 UTC

Last modified by the source

10 Sep 2026, 03:50 UTC

Source last checked

26 Oct 2026, 13:13 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-3f7w-p8vr-4v5f

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-3f7w-p8vr-4v5f

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-32880

Advisory: pyLoad allows upload to arbitrary folder lead to RCE
IDs: CVE-2024-32880, GHSA-3f7w-p8vr-4v5f
Record: https://patchnext.com/advisories/cve-2024-32880 (revision 2, source checked 26 Oct 2026, 13:13 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI pyload-ng: affected <= 0.5.0

## Suggested inspection (read-only)
- `python -m pip show pyload-ng`: prints the installed version. Run with the environment that serves production active.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on pyload-ng.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-3f7w-p8vr-4v5f (OSV record GHSA-3f7w-p8vr-4v5f lists affected ranges: PyPI pyload-ng >=0 <=0.5.0)
- Verified: https://github.com/advisories/GHSA-3f7w-p8vr-4v5f (GitHub-reviewed advisory GHSA-3f7w-p8vr-4v5f lists affected ranges: PyPI pyload-ng >=0 <=0.5.0)

Commands are suggestions: review each one before running it.