Skip to main content
Mallory
CriticalVulnerability

CVE-2020-12832: Arbitrary File Deletion in WordPress Simple File List

Published May 13, 2020 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS9.8Critical · v3.1
EPSS7.1%94th percentile
CISA KEVNoNot listed
In the wildReported374 exploitation records in Mallory
Vendor
Simplefilelist
IdentifiersCVE-2020-12832CWE-22 · Improper Limitation of a Pathname…

CVE-2020-12832 affects the WordPress Simple File List plugin before version 4.2.8. The plugin fails to properly validate user-supplied path input, allowing an attacker to traverse directories and target files outside the intended file-management scope. The provided content specifically states that the flaw can be used to delete arbitrary files. Although one supporting summary refers to path traversal for file access, the primary description identifies the security impact as arbitrary file deletion caused by improper verification of attacker-controlled input.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows an attacker to delete arbitrary files accessible to the web server or plugin context. Depending on target file selection and filesystem permissions, this can cause application disruption, loss of uploaded content, corruption of WordPress or plugin data, and potentially denial of service if critical application files are removed.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, restrict access to the plugin's file-management functionality, especially from untrusted or anonymous users; disable the plugin if it is not required; and harden filesystem permissions so the web server and WordPress process cannot delete sensitive files outside the intended upload or working directories. Monitoring for unexpected file deletions and requests containing traversal sequences may also reduce exposure.

Remediation

Patch, then assume compromise.

Upgrade the WordPress Simple File List plugin to version 4.2.8 or later. The vulnerable behavior is described as affecting versions before 4.2.8, so remediation is to deploy a fixed release that properly validates and constrains user-supplied file path input.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
SimplefilelistSimple File Listapplication
FAQ

Frequently asked questions

Is CVE-2020-12832 exploited in the wild?
Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2020-12832?
As of Oct 16, 2026, Mallory has found no public exploit for CVE-2020-12832.
Is there a patch for CVE-2020-12832?
Upgrade the WordPress Simple File List plugin to version 4.2.8 or later. The vulnerable behavior is described as affecting versions before 4.2.8, so remediation is to deploy a fixed release that properly validates and constrains user-supplied file path input.
What products are affected by CVE-2020-12832?
Simplefilelist Simple File List.
How severe is CVE-2020-12832?
CVE-2020-12832 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 7.1% (94th percentile) as of Oct 16, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signatures1YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity3Community discussion across Reddit, Mastodon, and other social sources.