WP Super Cache vulnerability history, and how to read its cache settings
WP Super Cache stores pages on the server as static files and, by its listing, serves them before almost all of WordPress is loaded.
Here are the vulnerability records the source data holds for it, and where to read its delivery method, cache location, rejected URL strings and cache-clearing settings.
On this page
WP Super Cache vulnerability history
Source: Wordfence Intelligence (Vulnerability Data Feed v3, Production), retrieved on . It lists 12 records for WP Super Cache. Copyright notices, licence terms and a link to each source record are under Data source and licence at the foot of this page.
Update to at least version 1.9
Worked out from data retrieved on .
Every affected range listed in this source for WP Super Cache ends before version 1.9.
A vendor can publish a security release before this source records it. Read the plugin's own changelog as well as this history.
WP Super Cache <= 1.8 - Unauthenticated Cache Poisoning
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.5)
Affected versions- All versions up to and including 1.8
Patched versions: 1.9
Update to at least version 1.9.
WP Super Cache <= 1.7.2 - Authenticated Remote Code Execution
- Published:
- Last updated:
- Severity:
- High (CVSS 7.2)
- CVE:
- CVE-2021-24312
Affected versions- All versions before 1.7.3
Patched versions: 1.7.3
Update to at least version 1.7.3.
WP Super Cache <= 1.7.2 - Authenticated (Admin+) Stored Cross-Site Scripting
- Published:
- Last updated:
- Severity:
- Medium (CVSS 4.8)
- CVE:
- CVE-2021-24329
Affected versions- All versions before 1.7.3
Patched versions: 1.7.3
Update to at least version 1.7.3.
WP Super Cache <= 1.7.1 - Authenticated (Admin+) Remote Code Execution
- Published:
- Last updated:
- Severity:
- High (CVSS 7.2)
- CVE:
- CVE-2021-24209
Affected versions- All versions before 1.7.2
Patched versions: 1.7.2
Update to at least version 1.7.2.
WP Super Cache <= 1.4.8 - Cross-Site Scripting
- Published:
- Last updated:
- Severity:
- Medium (CVSS 5.3)
Affected versions- All versions up to and including 1.4.8
Patched versions: 1.4.9
Update to at least version 1.4.9.
Show 7 older recordsHide the older records
WP Super Cache <= 1.4.4 - Directory Listing
- Published:
- Last updated:
- Severity:
- Medium (CVSS 5.3)
Affected versions- All versions before 1.4.5
Patched versions: 1.4.5
Update to at least version 1.4.5.
WP Super Cache <= 1.4.4 - Authenticated File Deletion
- Published:
- Last updated:
- Severity:
- Medium (CVSS 5.4)
Affected versions- All versions before 1.4.5
Patched versions: 1.4.5
Update to at least version 1.4.5.
WP Super Cache <= 1.4.4 - PHP Object Injection
- Published:
- Last updated:
- Severity:
- High (CVSS 8.1)
Affected versions- All versions before 1.4.5
Patched versions: 1.4.5
Update to at least version 1.4.5.
WP Super Cache < 1.4.3 - Cross Site Scripting
- Published:
- Last updated:
- Severity:
- High (CVSS 7.2)
Affected versions- All versions before 1.4.3
Patched versions: 1.4.3
Update to at least version 1.4.3.
WP Super Cache Plugin <= 1.3 - Multiple Cross-Site Scripting
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.1)
- CVE:
- CVE-2013-2008
Affected versions- All versions up to and including 1.3
Patched versions: 1.3.1
Update to at least version 1.3.1.
WP Super Cache < 1.3.2 - Remote Code Execution
- Published:
- Last updated:
- Severity:
- Critical (CVSS 9.8)
- CVE:
- CVE-2013-2011
Affected versions- All versions before 1.3.2
Patched versions: 1.3.2
Update to at least version 1.3.2.
WP Super Cache <= 1.2 - Remote Code Execution
- Published:
- Last updated:
- Severity:
- High (CVSS 8.8)
- CVE:
- CVE-2013-2009
Affected versions- All versions up to and including 1.2
Patched versions: 1.3
Update to at least version 1.3.
Check WP Super Cache on a live site
Read-only checks for a site you own or are authorised to review. Each step uses the WordPress dashboard or WP-CLI and sends no test payloads to the site.
Three ways WP Super Cache serves cached files, and who sets the rules
WP Super Cache, published by Automattic, generates static html files from a WordPress site, by the description on its WordPress.org listing.
The listing says the plugin serves cached files in three ways: Expert, through Apache mod_rewrite or whatever similar module the web server supports; Simple, through PHP, which the listing recommends; and WP-Cache caching, mainly used for known users, URLs with parameters and feeds.
Input reaches it from two directions. One is the visitor: the listing says of people who are logged in or have left comments that "those details will be displayed and cached for them". The other is the settings page at Settings > WP Super Cache, where the plugin's text labels boxes for Cache Location, Rejected URL Strings, Rejected Cookies and Always Cache Filenames.
On who works those settings, the listing says its REST API endpoints for them need "an admin user with permission to view the settings page". Jetpack's setup guide says that when the plugin is network-activated, each subsite administrator configures caching settings independently through their own Settings > WP Super Cache panel.
WP Super Cache vulnerabilities on record: Remote Code Execution, Cache Poisoning, Directory Listing
Remote Code Execution and Cross-Site Scripting each end more than one title in this history.
Each example here quotes a title's ending and gives that record's own fields.
- CVE-2021-24209. Title ends: Authenticated (Admin+) Remote Code Execution. Affected: all versions before 1.7.2. Patched: 1.7.2.
- CVE-2021-24312. Title ends: Authenticated Remote Code Execution. Affected: all versions before 1.7.3. Patched: 1.7.3.
- CVE-2013-2009. Title ends: Remote Code Execution. Affected: all versions up to and including 1.2. Patched: 1.3.
- A record with no CVE id. Title ends: Unauthenticated Cache Poisoning. Affected: all versions up to and including 1.8. Patched: 1.9.
- A record with no CVE id. Title ends: Directory Listing. Affected: all versions before 1.4.5. Patched: 1.4.5.
Fields first, titles second
Where a record has no CVE id, as with the one whose title ends Directory Listing, the title is the only name it has here. Where a title and a field differ, go by the field: the title of CVE-2021-24312 carries the version 1.7.2, while its affected range reads all versions before 1.7.3.
For CVE-2013-2009 the range ends at 1.2 and the patched versions field reads 1.3: the fields say nothing about the versions between the two, so for that record the patched version is the one to reach.
Before relying on the update guidance at the top of the history, read the changelog on the plugin's WordPress.org listing too: it is the vendor's own account of its recent releases, it has marked an entry with the word Security, and a release described there may have no record on this page.
Reading each WP Super Cache setting without changing it
These five checks read and change nothing.
The settings page is at Settings > WP Super Cache; the text of its easy page carries Update Status, Test Cache and Delete Cache buttons, and its Advanced and Lock Down text carries more, so press no button on any tab. For a site showing the error that the WPCACHEHOME constant must be set, the listing's troubleshooting notes say "it's easier to let the settings page fix it". On such a site, loading the page may change files, so use a staging copy.
WordPress documents the Description column of its Plugins screen as including each plugin's version number. Note the WP Super Cache figure, with the date and what the Automatic update column shows. On a multisite network, note whether the plugin is network-activated: Jetpack's setup guide says its drop-in file, wp-content/advanced-cache.php, loads on every page request across the entire network, regardless of which site activated the plugin.
In the Advanced text, write down three settings as labelled: Enable Caching; Cache Delivery Method, Simple (marked Recommended) or Expert; and Cache Restrictions, whose three choices include "Enable caching for all visitors" and "Disable caching for logged in visitors", the one marked Recommended.
The easy page's text says the settings it enables, Simple caching and caching disabled for logged in visitors among them, can be modified on the Advanced Settings page. Note whether "Make known users anonymous so they're served supercached static files" is ticked, and whether wp-config.php or an mu-plugin sets the constant DISABLE_SUPERCACHE to 1, which the listing's FAQ gives for a site that wants only the WP-Cache engine.
From outside, read the response headers of a signed-out page load: the listing's FAQ says PHP cached pages will have the header "WP-Super-Cache: Served supercache file from PHP" and WPCache cached files "WP-Super-Cache: Served WPCache cache file".
Cache Location holds a full path. The Advanced text gives the default as WP_CONTENT_DIR . /cache/, and the listing's FAQ says all cache files are stored under wp-content/cache/supercache/. Write down the path and whether it sits inside the web root. The text warns against "a shared directory like /tmp/ where other users on this server can modify files".
Copy in full any notice that the plugin "detected a bare directory index in your cache directory", and list any entries under Directly Cached Files, a section whose text calls them files created directly off the directory where the blog lives.
In the Advanced text, Rejected URL Strings holds strings that force a page not to be cached: "WP-Cache will search if that string is part of the URI and if so, it will not cache that page." Always Cache Filenames holds filenames that can be cached "even if they match one of the rejected substring".
Rejected Cookies is marked "Simple caching only". Copy all three, and the boxes ticked under "Do not cache the following page types".
Then set them beside the site's own addresses: an account, cart or checkout page should be covered by a string, a cookie or the Cache Restrictions choice.
The listing says that even with preload mode enabled, cached files will still be deleted when posts are modified or comments made. Its FAQ says that with the Cache Rebuild feature a cached page is not cleared when a comment is left but marked for rebuilding.
The Advanced text has tick boxes for cache rebuild and for "Clear all cache files when a post or page is published or updated". Record whether each is ticked, and whether the heading Lock Down reads Enabled, which that section's text says means new comments on a post will not refresh the cached static files.
Then list Editors and Authors from the Role column of the WordPress Users screen: WordPress documents an Author as able to publish its own posts, and an Editor other users' posts as well.
For each role you can sign in as, note whether any control for deleting the cache is on offer outside the settings page, without pressing it.
What a WP Super Cache version match leaves unread
The version number places a copy of WP Super Cache inside or outside each affected range in the history.
It is silent on whether any record's flaw was used against the site, on whose pages were stored while Cache Restrictions allowed caching for all visitors, and on whether debug logging was left on, which Jetpack's debugging guide says logs to a file in the cache directory.
Nor does it show what sits in wp-content/plugins/wp-super-cache-plugins, a directory the listing gives for adding to the plugin system WP Super Cache loads before most of WordPress.
A WordPress security audit adds checks a version number cannot stand in for: it checks for directory listings, looks for backup archives and copies of wp-config.php left in the web root, and on membership sites requests gated posts directly, as a logged-out visitor and as a member of a lower tier.
Frequently asked questions
Each record answers in its affected range and patched versions field. CVE-2021-24209 covers all versions before 1.7.2 and lists 1.7.2 as patched; the record whose title ends Unauthenticated Cache Poisoning covers all versions up to and including 1.8 and lists 1.9. Check your version against every affected range in the history, and read the changelog on the WordPress.org listing before treating the update guidance at the top of the history as the whole answer: the changelog may describe a release that has no record here.
Before any update, look inside wp-super-cache/plugins/: the listing's FAQ says WordPress deletes the plugin folder when it updates a plugin, so any modified files there will be deleted. For the version, set the figure from the WordPress Plugins screen beside the update guidance at the top of the history, and read the changelog on the WordPress.org listing as well: a release described there may have no record on this page.
The listing's uninstall notes say the plugin should clean up most of the files it created and modified but does not as yet remove its mod_rewrite rules from .htaccess. Its own uninstall steps include removing the WP_CACHE define from wp-config.php, the files wp-content/advanced-cache.php and wp-content/wp-cache-config.php, and the directory wp-content/cache/.
The plugin's own text gives three choices under Cache Restrictions: "Enable caching for all visitors", "Disable caching for visitors who have a cookie set in their browser" and "Disable caching for logged in visitors", the last marked Recommended. Its easy page lists "Caching disabled for logged in visitors" among the recommended settings it says will be enabled. The listing defines known users as logged in users, visitors who leave comments or those who should be shown custom per-user data. A separate tick box reads "Make known users anonymous so they're served supercached static files": write down its state beside the Cache Restrictions choice.
Scope the right test for your application
Tell us what you have built, who uses it and when it needs to launch. You will get a plain-English recommendation: a website audit, a web application test or a referral to a specialist.
Data source and licenceHide the data source and licence
The vulnerability records on this page come from Wordfence Intelligence (Vulnerability Data Feed v3, Production), retrieved on . The records contain material that is subject to copyright. Each copyright notice and its licence are reproduced once below, followed by a link to every source record.
Copyright 2012-2026 Defiant Inc.
Applies to every record listed below.
Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.
Copyright 1999-2026 The MITRE Corporation
Applies to 6 of the 12 records listed below.
CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.
Source records
- WP Super Cache <= 1.8 - Unauthenticated Cache Poisoning
- WP Super Cache <= 1.7.2 - Authenticated Remote Code Execution (CVE-2021-24312)
- WP Super Cache <= 1.7.2 - Authenticated (Admin+) Stored Cross-Site Scripting (CVE-2021-24329)
- WP Super Cache <= 1.7.1 - Authenticated (Admin+) Remote Code Execution (CVE-2021-24209)
- WP Super Cache <= 1.4.8 - Cross-Site Scripting
- WP Super Cache <= 1.4.4 - Directory Listing
- WP Super Cache <= 1.4.4 - Authenticated File Deletion
- WP Super Cache <= 1.4.4 - PHP Object Injection
- WP Super Cache < 1.4.3 - Cross Site Scripting
- WP Super Cache Plugin <= 1.3 - Multiple Cross-Site Scripting (CVE-2013-2008)
- WP Super Cache < 1.3.2 - Remote Code Execution (CVE-2013-2011)
- WP Super Cache <= 1.2 - Remote Code Execution (CVE-2013-2009)