How severe is CVE-2020-24186?

CVE-2020-24186 has a CVSS score of 10/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2020-24186?

Affected package information for CVE-2020-24186 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2020-24186?

No fixed release is recorded for CVE-2020-24186 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.

How do I detect CVE-2020-24186 in my code and dependencies?

Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).

How do I mitigate CVE-2020-24186 if there is no patch (or I can't update yet)?

Treat uploaded files as untrusted until proven otherwise: validate the actual content type rather than the supplied extension, store uploads outside the web root on a volume mounted without execute permission, and rename them to server-generated identifiers so an attacker cannot choose the path a request will later resolve.

Is CVE-2020-24186 actively exploited in the wild?

Yes. There are 15 known exploit references for CVE-2020-24186, including 2 documented proof-of-concept exploits on Exploit-DB and 10 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2020-24186?

CVE-2020-24186 has an EPSS (Exploit Prediction Scoring System) score of 94.6%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is CVE-2020-24186?

CVE-2020-24186 is classified as Unrestricted File Upload (CWE-434). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Is there exploit tooling available for CVE-2020-24186?

A Nuclei detection template exists for CVE-2020-24186, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2020-24186 published, and has it been updated?

CVE-2020-24186 was published on August 24, 2020 and was last updated on August 4, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🛡️

Not in CISA KEV

CRITICAL severity

CVE-2020-24186

CRITICAL

CVE-2020-24186 is a critical-severity (CVSS 10) Unrestricted File Upload vulnerability. 15 public exploit references exist, so weaponization risk is real. No vendor fix is recorded yet; mitigation options are listed below.

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…

Published

Aug 24, 2020

Updated

Aug 4, 2024

Affected

1 product

Patched

See advisory

Exploits

15 known

Exploitation data as of Oct 21, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

94.6%probability of exploitation in next 30 days

Very High Risk0.00%

Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2020-24186 by exploitation likelihood (EPSS) against impact (CVSS). In the shaded patch-first corner (EPSS 50%+, CVSS 7.0+).

Where this sits among everything scored

Of 394,415 CVEs with a current EPSS score, this one falls in the ≥ 90% band (highlighted). Counts from FIRST.org, log-scaled.

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.

Affected Products

1 product · 1 configurations

Application

wpdiscuzgvectors

≥ 7.0 && ≤ 7.0.4

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-49967webappsphp

WordPress Plugin wpDiscuz 7.0.4 - Remote Code Execution (Unauthenticated)

by Fellipe Oliveira · Jun 8, 2021

Exploit-DB Source

EDB-49962webappsphp

Wordpress Plugin wpDiscuz 7.0.4 - Arbitrary File Upload (Unauthenticated)

by UnD3sc0n0c1d0 · Jun 7, 2021

Exploit-DB Source

Detection & mitigation playbook

Vulnerability

Detect
Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).
Remediation status
No fixed release is recorded for CVE-2020-24186 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.
Mitigate without a patch
Treat uploaded files as untrusted until proven otherwise: validate the actual content type rather than the supplied extension, store uploads outside the web root on a volume mounted without execute permission, and rename them to server-generated identifiers so an attacker cannot choose the path a request will later resolve.

How to detect CVE-2020-24186

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id cve-2020-24186 -u https://target

Template: WordPress wpDiscuz <=7.0.4 - Remote Code Execution
Severity: critical
Impact: Successful exploitation of this vulnerability can lead to arbitrary code execution on the affected WordPress site.
Remediation: Update the wpDiscuz plugin to the latest version (>=7.0.5) to mitigate this vulnerability.

Template by ProjectDiscovery nuclei-templates (Ganofins), MIT licensed. View the full template. Scan only systems you are authorised to test.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2020-24186 in your dependencies?

Find it across , including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

10/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Changed

Confidentiality

High

Integrity

High

Availability

High

Raw vector

CVSS:3.1/AC:L/AV:N/A:H/C:H/I:H/PR:N/S:C/UI:N

CWE Classification

CWE-434Unrestricted File Upload

Weaponization

Timeline

Disclosed

Aug 24, 2020

First exploit

Jun 8, 2021

Last updated

Aug 4, 2024

Identifiers

CVE-2020-24186

References

Webwordfence.com Webpacketstormsecurity.com Webpacketstormsecurity.com Webpacketstormsecurity.com

Related vulnerabilities

This CVE is critical severity; 1 of 8 other CVEs with CWE-434 is rated as high or higher (top: critical).

CVE-2026-105862CVE-2026-105651CVE-2026-105649CVE-2026-105868CVE-2026-105679CVE-2026-105644CVE-2026-104890GHSA-v2f8-6655-7grjBrowse all CWE-434

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedAug 4, 2024

CVE-2020-24186

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Description

Affected Products

Detection & mitigation playbook

Detect

Remediation status

Mitigate without a patch

How to detect CVE-2020-24186

Frequently Asked Questions

Is CVE-2020-24186 in your dependencies?