How severe is CVE-2020-12800?

No CVSS score has been assigned to CVE-2020-12800 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2020-12800?

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

How do I fix CVE-2020-12800?

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

How do I detect CVE-2020-12800 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-12800 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-12800 actively exploited in the wild?

Yes. There are 5 known exploit references for CVE-2020-12800, including 4 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-12800?

CVE-2020-12800 has an EPSS (Exploit Prediction Scoring System) score of 78.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-12800?

CVE-2020-12800 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-12800?

A Nuclei detection template exists for CVE-2020-12800, meaning automated scanners can fingerprint it. A Metasploit module references CVE-2020-12800, which lowers the barrier to weaponization. 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-12800 published, and has it been updated?

CVE-2020-12800 was published on June 8, 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

CVE-2020-12800 — WordPress

CVE-2020-12800 is a Unrestricted File Upload vulnerability. 5 public exploit references exist, so weaponization risk is real. No vendor fix is recorded yet; mitigation options are listed below.

The drag-and-drop-multiple-file-upload-contact-form-7 plugin before 1.3.3.3 for WordPress allows Unrestricted File Upload and remote code execution by setting supported_type to php%…

Published

Jun 8, 2020

Updated

Aug 4, 2024

Affected

1 product

Patched

See advisory

Exploits

5 known

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

EPSS Exploitation Probability

via FIRST.org ↗

78.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.

Description

The drag-and-drop-multiple-file-upload-contact-form-7 plugin before 1.3.3.3 for WordPress allows Unrestricted File Upload and remote code execution by setting supported_type to php% and uploading a .php% file.

Affected Products

1 product · 1 configurations

Application

drag and drop multiple file upload - contact form 7codedropz

< 1.3.3.3

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.

The drag-and-drop-multiple-file-upload-contact-form-7 plugin before 1.3.…

packetstormsecurity.comNVDJun 2020

The drag-and-drop-multiple-file-upload-contact-form-7 plugin before 1.3.…

github.comMetasploitAug 2021

The drag-and-drop-multiple-file-upload-contact-form-7 plugin before 1.3.…

github.comGithubMay 2020

The drag-and-drop-multiple-file-upload-contact-form-7 plugin before 1.3.…

unit42.paloaltonetworks.comAPIApr 2021

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-12800 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-12800

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

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

Template: WordPress Contact Form 7 <1.3.3.3 - Remote Code Execution
Severity: critical
Impact: Successful exploitation of this vulnerability allows remote attackers to execute arbitrary code on the affected WordPress site.
Remediation: Update the Contact Form 7 plugin to version 1.3.3.3 or later to mitigate this vulnerability.

Template by ProjectDiscovery nuclei-templates (dwisiswant0), 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-12800 in your dependencies?

Find it across , including transitive dependencies.

Scan my dependencies How O3 SCA works

CVE-2020-12800 — WordPress

EPSS Exploitation Probability

Description

Affected Products

Detection & mitigation playbook

Detect

Remediation status

Mitigate without a patch

How to detect CVE-2020-12800

Frequently Asked Questions

Is CVE-2020-12800 in your dependencies?