# CVE-2020-20124: Code injection in n/a

> Attackers can execute arbitrary code remotely via a vulnerability in the attachment admin module of Wuzhi CMS.

- **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:** 28 Sep 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-99g3-m7v3-fpm5

## What is CVE-2020-20124?

CVE-2020-20124 is a high-severity code injection vulnerability in Wuzhicms Wuzhicms, published on 28 Sep 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Wuzhi CMS v4.1.0 contains a remote code execution (RCE) vulnerability in \attachment\admin\index.php.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: Wuzhicms Wuzhicms.

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

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

## Is CVE-2020-20124 being exploited?

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

## Other vulnerabilities in Wuzhicms Wuzhicms

- [CVE-2023-52064](https://insights.sbomify.com/CVE-2023-52064/): SQL injection in n/a (critical 9.8)
- [CVE-2023-46482](https://insights.sbomify.com/CVE-2023-46482/): SQL injection in n/a (critical 9.8)
- [CVE-2020-20413](https://insights.sbomify.com/CVE-2020-20413/): SQL injection in n/a (critical 9.8)
- [CVE-2021-41654](https://insights.sbomify.com/CVE-2021-41654/): SQL injection in n/a (critical 9.8)
- [CVE-2022-27431](https://insights.sbomify.com/CVE-2022-27431/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-20124 is a high-severity code injection vulnerability in Wuzhicms Wuzhicms, published on 28 Sep 2021. 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-20124 in the wild and no public exploit code.

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

## Sources

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

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