# CVE-2024-50919: File upload in n/a

> Attackers can upload malicious files to execute arbitrary commands on Jpress installations running on Windows platforms.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Nov 2024
- **Updated:** 19 Nov 2024
- **Also known as:** GHSA-8vf7-6fh2-6qw4

## What is CVE-2024-50919?

CVE-2024-50919 is a critical vulnerability in n/a, published on 18 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Jpress until v5.1.1 has arbitrary file uploads on the windows platform, and the construction of non-standard file formats such as .jsp. can lead to arbitrary command execution

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: Jpress Jpress.

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

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

## Is CVE-2024-50919 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-45807](https://insights.sbomify.com/CVE-2021-45807/): Command injection in n/a (critical 9.8)
- [CVE-2024-43033](https://insights.sbomify.com/CVE-2024-43033/): File upload in n/a (high 8.8)
- [CVE-2022-23330](https://insights.sbomify.com/CVE-2022-23330/): Code injection in n/a (high 8.8)
- [CVE-2021-46114](https://insights.sbomify.com/CVE-2021-46114/): Code injection in n/a (high 8.8)
- [CVE-2021-45808](https://insights.sbomify.com/CVE-2021-45808/): File upload in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-50919 is a critical vulnerability in n/a, published on 18 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-50919 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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