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

> Remote attackers can execute arbitrary code by uploading a crafted zip file via the assets parameter in Fuel-CMS.

- **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:** 3 Jul 2023
- **Updated:** 25 Nov 2024
- **Also known as:** GHSA-ww86-3cc2-9g27

## What is CVE-2020-22151?

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

### Official description

Permissions vulnerability in Fuel-CMS v.1.4.6 allows a remote attacker to execute arbitrary code via a crafted zip file to the assests parameter of the upload function.

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

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

It affects 1 product.


Products: Thedaylightstudio Fuel Cms.

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

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

## Is CVE-2020-22151 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-17463](https://insights.sbomify.com/CVE-2020-17463/): Fuel CMS SQL Injection (critical 9.8, exploited in the wild)
- [CVE-2020-22153](https://insights.sbomify.com/CVE-2020-22153/): File upload in n/a (critical 9.8)
- [CVE-2021-38727](https://insights.sbomify.com/CVE-2021-38727/): SQL injection in n/a (critical 9.8)
- [CVE-2020-24791](https://insights.sbomify.com/CVE-2020-24791/): SQL injection in n/a (critical 9.8)
- [CVE-2020-26045](https://insights.sbomify.com/CVE-2020-26045/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-22151 is a critical vulnerability in n/a, published on 3 Jul 2023. 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-2020-22151 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-2020-22151/ (Markdown: https://insights.sbomify.com/CVE-2020-22151/index.md)
```

## Sources

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

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