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

> Attackers can execute arbitrary code by uploading a crafted HTML file to the media upload endpoint in ZKEACMS.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 13 Sep 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-w2gx-ph96-cxcc

## What is CVE-2020-20670?

CVE-2020-20670 is a high-severity vulnerability in n/a, published on 13 Sep 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

An arbitrary file upload vulnerability in /admin/media/upload of ZKEACMS V3.2.0 allows attackers to execute arbitrary code via a crafted HTML file.

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

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

It affects 1 product.


Products: Zkea Zkeacms.

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

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

## Is CVE-2020-20670 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-52239](https://insights.sbomify.com/CVE-2025-52239/): File upload in n/a (critical 9.8)
- [CVE-2022-29362](https://insights.sbomify.com/CVE-2022-29362/): Cross-site Scripting in ZKEACMS (medium 5.4)
- [CVE-2025-10764](https://insights.sbomify.com/CVE-2025-10764/): SeriaWei ZKEACMS Event Action System PendingTaskController.cs Edit server-side request forgery (medium 5.3)
- [CVE-2025-10766](https://insights.sbomify.com/CVE-2025-10766/): SeriaWei ZKEACMS EventViewerController.cs Download path traversal (medium 5.3)
- [CVE-2025-10471](https://insights.sbomify.com/CVE-2025-10471/): ZKEACMS MediaController.cs Proxy server-side request forgery (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-20670 is a high-severity vulnerability in n/a, published on 13 Sep 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-20670 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-20670/ (Markdown: https://insights.sbomify.com/CVE-2020-20670/index.md)
```

## Sources

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

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