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

> Authenticated attackers can upload malicious PHP code via theme zip files in HorizontCMS, leading to remote code execution.

- **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:** 16 Nov 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-p5vc-h7j2-25qc

## What is CVE-2020-28693?

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

### Official description

An unrestricted file upload issue in HorizontCMS 1.0.0-beta allows an authenticated remote attacker to upload PHP code through a zip file by uploading a theme, and executing the PHP file via an HTTP GET request to /themes/<php_file_name>

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

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

It affects 1 product.


Products: Horizontcms Project Horizontcms.

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

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

## Is CVE-2020-28693 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-28428](https://insights.sbomify.com/CVE-2021-28428/): File upload in n/a (critical 9.8)
- [CVE-2020-27387](https://insights.sbomify.com/CVE-2020-27387/): File upload in n/a (high 8.8)
- [CVE-2022-25104](https://insights.sbomify.com/CVE-2022-25104/): Path traversal in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-28693 is a high-severity vulnerability in n/a, published on 16 Nov 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-28693 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-28693/ (Markdown: https://insights.sbomify.com/CVE-2020-28693/index.md)
```

## Sources

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

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