# CVE-2020-24199: File upload in n/a

> Attackers can upload arbitrary files to the Vehicle Image Upload component, leading to remote code execution.

- **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:** 9 Sep 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-6cmx-4cq4-q68g

## What is CVE-2020-24199?

CVE-2020-24199 is a critical vulnerability in n/a, published on 9 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Arbitrary File Upload in the Vehicle Image Upload component in Project Worlds Car Rental Management System v1.0 allows attackers to conduct remote code execution.

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

## Which versions are affected by CVE-2020-24199?

It affects 1 product.


Products: Projectworlds Car Rental Project.

## How do I fix CVE-2020-24199?

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

## Is CVE-2020-24199 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2026-5368](https://insights.sbomify.com/CVE-2026-5368/): projectworlds Car Rental Project Parameter login.php sql injection (medium 6.9)
- [CVE-2025-4456](https://insights.sbomify.com/CVE-2025-4456/): Project Worlds Car Rental Project signup.php sql injection (medium 6.9)
- [CVE-2025-4457](https://insights.sbomify.com/CVE-2025-4457/): Project Worlds Car Rental Project approve.php sql injection (medium 6.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-24199 and fix it if it is affected.

What it is: CVE-2020-24199 is a critical vulnerability in n/a, published on 9 Sep 2020. 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-2020-24199 in the wild and no public exploit code.

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

## Sources

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

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