CVE-2020-36836: The WP Fastest Cache plugin for WordPress is vulnerable to unauthorized arbitrary file deletion in versions up

Q: How do I fix CVE-2020-36836?

wp fastest cache: upgrade to 0.9.0.3. Exact commands for each OS are on this page.

Q: Is CVE-2020-36836 being exploited?

CVE-2020-36836 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2020-36836 affect?

CVE-2020-36836 affects wp fastest cache. Severity is high (CVSS 8.0). The WP Fastest Cache plugin for WordPress is vulnerable to unauthorized arbitrary file deletion in versions up to, and including, 0.9.0.2 due to a lack of capability checking and insufficient path validation. This makes it possible for auth

Q: How urgent is CVE-2020-36836?

Priority 52/100. High severity; Public exploit reference

This month

HIGH 8.0UPGRADE

CVE-2020-36836 is a high-severity flaw (CVSS 8.0) affecting wp fastest cache. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The WP Fastest Cache plugin for WordPress is vulnerable to unauthorized arbitrary file deletion in versions up to, and including, 0.9.0.2 due to a lack of capability checking and insufficient path validation. This makes it possible for authenticated users with minimal permissions to delete arbitrary files from the server.

Why this priority

High severity
Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	8.0 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	Required
EPSS exploit chance	1.5% (top 26%)
CISA exploited list	No
Weakness	CWE-352, CWE-22
Published	2024-10-16
Last modified	2026-06-17

Publisher (CNA): Wordfence · Vendor: wpfastestcache

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2024-10-16 07:15 UTCPublished CVE record published
2026-06-17 03:16 UTCUpdated Record last modified

wpfastestcache wp fastest cache UPGRADE

Affected: < 0.9.0.3

Fixed in: 0.9.0.3

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy wp-fastest-cache || rpm -q wp-fastest-cache || wp-fastest-cache --version

2. UPGRADE to 0.9.0.3 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade wp-fastest-cache

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade wp-fastest-cache

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

Nuclei scan template: WordPress WP Fastest Cache <= 0.9.0.2 - Authenticated Arbitrary File Deletion

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2020-36836?

wp fastest cache: upgrade to 0.9.0.3. Exact commands for each OS are on this page.

Is CVE-2020-36836 being exploited?

CVE-2020-36836 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2020-36836 affect?

CVE-2020-36836 affects wp fastest cache. Severity is high (CVSS 8.0). The WP Fastest Cache plugin for WordPress is vulnerable to unauthorized arbitrary file deletion in versions up to, and including, 0.9.0.2 due to a lack of capability checking and insufficient path validation. This makes it possible for auth

How urgent is CVE-2020-36836?

Priority 52/100. High severity; Public exploit reference

Software pages

WordPress vulnerabilities

Related CVEs

CVE-2023-6063 HIGH 7.5 UPGRADE The WP Fastest Cache WordPress plugin before 1.2.2 does not properly sanitise and escape a parameter before us
CVE-2023-1375 MEDIUM 4.3 UPGRADE The WP Fastest Cache plugin for WordPress is vulnerable to unauthorized cache deletion in versions up to, and

References

← Back to latest CVEs