# CVE-2023-47890: Download to arbitrary folder can lead to RCE

> Attackers can upload arbitrary files to pyLoad, potentially leading to remote code execution on the host system.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Jan 2024
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-h73m-pcfw-25h2, PYSEC-2026-1819

## What is CVE-2023-47890?

CVE-2023-47890 is a high-severity vulnerability in n/a, published on 8 Jan 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

pyLoad 0.5.0 is vulnerable to Unrestricted File Upload.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2023-47890?

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 | 0.5.0b3.dev75 |
| `pyload-ng` | PyPI | All versions | 0.5.0b3.dev75 |
| `pyload-ng` | PyPI | All versions | 0.5.0b3.dev75 |

Products: Pyload Pyload.

## How do I fix CVE-2023-47890?

Upgrade pyload-ng to 0.5.0b3.dev75 or later.

## Is CVE-2023-47890 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-47890 exists.

## Other vulnerabilities in n/a

- [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-2024-32880](https://insights.sbomify.com/CVE-2024-32880/): pyLoad allows upload to arbitrary folder lead to RCE (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)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-47890 and fix it if it is affected.

What it is: CVE-2023-47890 is a high-severity vulnerability in n/a, published on 8 Jan 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-47890 exists.

Affected packages and fixed versions:
- pyload-ng (PyPI): affected all versions; fixed in 0.5.0b3.dev75
- pyload-ng (PyPI): affected all versions; fixed in 0.5.0b3.dev75
- pyload-ng (PyPI): affected all versions; fixed in 0.5.0b3.dev75

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-2023-47890/ (Markdown: https://insights.sbomify.com/CVE-2023-47890/index.md)
```

## Sources

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

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