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

> Unauthenticated attackers can upload arbitrary files, including PHP scripts, leading to remote code execution on WordPress sites using the wpDiscuz plugin.

- **Severity:** Critical 10.0 (`CVSS:3.1/AC:L/AV:N/A:H/C:H/I:H/PR:N/S:C/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Aug 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-c73j-6x9h-mrv2

## What is CVE-2020-24186?

CVE-2020-24186 is a critical vulnerability in n/a, published on 24 Aug 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A Remote Code Execution vulnerability exists in the gVectors wpDiscuz plugin 7.0 through 7.0.4 for WordPress, which allows unauthenticated users to upload any type of file, including PHP files via the wmuUploadFiles AJAX action.

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

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

It affects 1 product.


Products: Gvectors Wpdiscuz.

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

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

## Is CVE-2020-24186 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-24186 exists.

Public exploit code:

- wpDiscuz 7.0.4 Remote Code Execution (github_poc): https://github.com/hev0x/CVE-2020-24186-wpDiscuz-7.0.4-RCE
- https://github.com/substing/CVE-2020-24186_reverse_shell_upload (github_poc): https://github.com/substing/CVE-2020-24186_reverse_shell_upload
- CVE-2020-24186的攻击脚本 (github_poc): https://github.com/Sakura-501/CVE-2020-24186-exploit
- WordPress wpDiscuz Unauthenticated File Upload Vulnerability (metasploit)
- Wordpress Plugin wpDiscuz 7.0.4 - Arbitrary File Upload (Unauthenticated) (exploitdb)
- WordPress Plugin wpDiscuz 7.0.4 - Remote Code Execution (Unauthenticated) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2024-9488](https://insights.sbomify.com/CVE-2024-9488/): Comments – wpDiscuz <= 7.6.24 - Authentication Bypass via WordPress.com OAuth provider (critical 9.8)
- [CVE-2020-13640](https://insights.sbomify.com/CVE-2020-13640/): SQL injection in n/a (critical 9.8)
- [CVE-2026-22193](https://insights.sbomify.com/CVE-2026-22193/): wpDiscuz before 7.6.47 - SQL Injection in getAllSubscriptions() (critical 9.2)
- [CVE-2026-22192](https://insights.sbomify.com/CVE-2026-22192/): Voltronic Power SNMP Web Pro 1.1 Authentication Bypass via localStorage (high 8.8)
- [CVE-2026-22182](https://insights.sbomify.com/CVE-2026-22182/): wpDiscuz before 7.6.47 - Unauthenticated Email Notification Flood via wpdCheckNotificationType (high 8.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-24186 is a critical vulnerability in n/a, published on 24 Aug 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-24186 exists.

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

## Sources

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

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