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

> Remote attackers can execute arbitrary code in HisiPHP by exploiting an access control flaw in the plugin upload directory handling.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Apr 2022
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-29rm-7h6p-fjf3

## What is CVE-2020-28062?

CVE-2020-28062 is a high-severity vulnerability in n/a, published on 4 Apr 2022. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

An Access Control vulnerability exists in HisiPHP 2.0.11 via special packets that are constructed in $files = Dir::getList($decompath. '/ Upload/Plugins /, which could let a remote malicious user execute arbitrary code.

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

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

It affects 1 product.


Products: Hisiphp Hisiphp.

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

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

## Is CVE-2020-28062 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-33445](https://insights.sbomify.com/CVE-2024-33445/): Code injection in n/a (critical 9.8)
- [CVE-2018-17826](https://insights.sbomify.com/CVE-2018-17826/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2018-17827](https://insights.sbomify.com/CVE-2018-17827/): Code injection in n/a (high 7.2)
- [CVE-2020-21130](https://insights.sbomify.com/CVE-2020-21130/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2019-1010193](https://insights.sbomify.com/CVE-2019-1010193/): Cross-site scripting in hisiphp (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-28062 is a high-severity vulnerability in n/a, published on 4 Apr 2022. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-28062 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-28062/ (Markdown: https://insights.sbomify.com/CVE-2020-28062/index.md)
```

## Sources

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

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