# CVE-2024-0864: RCE in Laragon

> Attackers can achieve remote code execution in Laragon if the Simple Ajax Uploader plugin is enabled, due to improper input validation in file uploads.

- **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:** 29 Feb 2024
- **Updated:** 10 Oct 2024
- **Also known as:** GHSA-4g4j-672p-6638

## What is CVE-2024-0864?

CVE-2024-0864 is a critical vulnerability in Leo Khoa Laragon, published on 29 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Enabling Simple Ajax Uploader plugin included in Laragon open-source software allows for a remote code execution (RCE) attack via an improper input validation in a file_upload.php file which serves as an example.
By default, Laragon is not vulnerable until a user decides to use the aforementioned plugin.

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

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

It affects 1 product.


Products: Laragon Laragon.

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

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

## Is CVE-2024-0864 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-0864 is a critical vulnerability in Leo Khoa Laragon, published on 29 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-0864 in the wild and no public exploit code.

Affected product: Leo Khoa Laragon. 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-0864/ (Markdown: https://insights.sbomify.com/CVE-2024-0864/index.md)
```

## Sources

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

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