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

> Attackers can achieve remote code execution by uploading malicious PHP files disguised as images due to insufficient file validation in rConfig.

- **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:** No
- **Published:** 18 May 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-5rv6-786c-qwh8

## What is CVE-2020-12255?

CVE-2020-12255 is a high-severity vulnerability in n/a, published on 18 May 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

rConfig 3.9.4 is vulnerable to remote code execution due to improper validation in the file upload functionality. vendor.crud.php accepts a file upload by checking content-type without considering the file extension and header. Thus, an attacker can exploit this by uploading a .php file to vendor.php that contains arbitrary PHP code and changing the content-type to image/gif.

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

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

It affects 1 product.


Products: Rconfig Rconfig.

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

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

## Is CVE-2020-12255 being exploited?

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

Public exploit code:

- Poc for CVE-2020-12255 (github_poc): https://github.com/vishwaraj101/CVE-2020-12255

## Other vulnerabilities in n/a

- [CVE-2020-10221](https://insights.sbomify.com/CVE-2020-10221/): rConfig OS Command Injection (high 8.8, exploited in the wild)
- [CVE-2020-15715](https://insights.sbomify.com/CVE-2020-15715/): Command injection in n/a (critical 9.9)
- [CVE-2020-23151](https://insights.sbomify.com/CVE-2020-23151/): Command injection in n/a (critical 9.8)
- [CVE-2020-13638](https://insights.sbomify.com/CVE-2020-13638/): Auth bypass in n/a (critical 9.8)
- [CVE-2020-10546](https://insights.sbomify.com/CVE-2020-10546/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-12255 is a high-severity vulnerability in n/a, published on 18 May 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-12255 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-12255/ (Markdown: https://insights.sbomify.com/CVE-2020-12255/index.md)
```

## Sources

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

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