CVE-2021-24869 is a high severity (CVSS 8.8) SQL injection in the WP Fastest Cache plugin for WordPress, in versions before 0.9.5. The set_urls_with_terms method uses input in a SQL statement without escaping it. Update to 0.9.5 or later.
What's affected
- WP Fastest Cache (wp-fastest-cache), versions before 0.9.5, per the NVD record.
- Fixed in 0.9.5, per the Jetpack write-up, which says the plugin author released it after being contacted.
- Source conflict: NVD scores it 8.8 (High) and says low privilege users such as subscribers can exploit it. Jetpack lists CVSS 7.7, calls it authenticated, and says it can only be exploited if the classic-editor plugin is also installed and active.
- The Jetpack write-up also reports a separate stored cross site scripting issue through cross site request forgery, fixed in the same release.
- KEV status: false.
How to check if you're exposed
Check the plugin version.
wp plugin list --fields=name,status,version
If wp-fastest-cache is below 0.9.5, it is affected. Check whether classic-editor is also active, since Jetpack states that combination is required, and note the NVD record does not mention that condition.
What to do now
- Update WP Fastest Cache to 0.9.5 or later.
- Do not rely on the classic-editor condition for safety. Update regardless.
- Limit open registration and review low privilege accounts, since the record says subscribers can reach the flaw.
- Check administrator accounts and recent changes, because Jetpack also reports a related cross site scripting issue.
- Review the database for unexpected users or options if you ran an affected version on a public site.
Why it matters
The class is CWE-89, SQL injection. The record says the plugin does not escape user input in the set_urls_with_terms method before it goes into a SQL statement. Database access from a low privilege account can expose private data, according to Jetpack, such as usernames and password hashes.
The two sources differ on who can use the bug and under what conditions. When sources differ on exploit conditions, plan around the wider reading and patch. The cost of updating a cache plugin is small compared to the cost of finding out the narrower reading was wrong.
For WordPress sites in general, keep an inventory of installed plugins with their versions, delete the ones you do not use, and apply updates on a schedule. Most plugin flaws are fixed quickly by their authors, and the sites that get hurt are mostly the ones that never applied the fix. A weekly check with WP-CLI takes a few minutes and covers most of the risk.
Quick check
Do I need classic-editor active for exposure?
Jetpack says so. The NVD record does not mention it. Update anyway.
Which version fixes it?
0.9.5, according to the Jetpack write-up.
Sources
- Jetpack write-up on WP Fastest Cache vulnerabilities
- WPScan entry listed in the record (not retrieved)
Last reviewed: 19 October 2026.