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

> Remote attackers can upload arbitrary files to SEMCMS PHP to execute code and escalate privileges.

- **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:** 30 Jun 2023
- **Updated:** 26 Nov 2024
- **Also known as:** GHSA-hg72-f8x2-chjh

## What is CVE-2020-18432?

CVE-2020-18432 is a critical vulnerability in Sem-Cms Semcms, published on 30 Jun 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

File Upload vulnerability in SEMCMS PHP 3.7 allows remote attackers to upload arbitrary files and gain escalated privileges.

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

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

It affects 1 product.


Products: Sem-Cms Semcms.

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

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

## Is CVE-2020-18432 being exploited?

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

## Other vulnerabilities in Sem-Cms Semcms

- [CVE-2025-25686](https://insights.sbomify.com/CVE-2025-25686/): SQL injection in n/a (critical 9.8)
- [CVE-2024-46103](https://insights.sbomify.com/CVE-2024-46103/): SQL injection in n/a (critical 9.8)
- [CVE-2024-30938](https://insights.sbomify.com/CVE-2024-30938/): SQL injection in n/a (critical 9.8)
- [CVE-2024-31012](https://insights.sbomify.com/CVE-2024-31012/): File upload in n/a (critical 9.8)
- [CVE-2024-25422](https://insights.sbomify.com/CVE-2024-25422/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-18432 is a critical vulnerability in Sem-Cms Semcms, published on 30 Jun 2023. 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-18432 in the wild and no public exploit code.

Affected product: Sem-Cms Semcms. 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-18432/ (Markdown: https://insights.sbomify.com/CVE-2020-18432/index.md)
```

## Sources

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

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