Super Page CacheWordPress extension · Optimole
CVE-2024-27968
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCross-Site Request Forgery (CSRF) vulnerability in Optimole Super Page Cache for Cloudflare allows Stored XSS.This issue affects Super Page Cache for Cloudflare: from n/a through 4.7.5.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceCross-Site Request Forgery (CSRF) vulnerability in Optimole's Super Page Cache for Cloudflare plugin allows attackers to inject malicious scripts through stored XSS. The lack of proper CSRF token validation on state-changing actions enables authenticated attackers to trick administrators into performing unintended actions that store malicious payloads.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Super Page CacheWordPress extension
<= 4.7.5CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Optimole Super Page Cache plugin is installedAccess WordPress admin dashboard, navigate to Plugins > Installed Plugins, and locate 'Optimole Super Page Cache for Cloudflare' in the listAffected if Plugin is present in the WordPress installation
-
Determine installed plugin versionIn the plugins list, click 'View Details' on the Optimole Super Page Cache plugin or inspect the main plugin PHP file (typically in wp-content/plugins/super-page-cache-for-cloudflare/) and locate the 'Version' header or $version variableAffected if Reported version is 4.7.5 or lower
-
Confirm admin access for state-changing actionsLog into WordPress admin area and navigate to the plugin settings page (usually under Settings > Super Page Cache or a dedicated Optimole menu item)Affected if Admin can access and modify plugin settings such as cache behavior, purge actions, or configuration options
-
Check for CSRF protection mechanismsInspect the plugin source code for nonce validation on form submissions and AJAX actions - look for wp_nonce_field(), check_admin_referer(), or nonce verification in PHP files handling state changesAffected if State-changing forms and actions lack proper nonce/token validation or do not verify Origin/Referer headers
User is affected if the Optimole Super Page Cache for Cloudflare plugin version is 4.7.5 or lower and the admin interface exposes state-changing actions without CSRF protection.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement anti-CSRF tokens (nonces) on all state-changing operations and validate the Origin/Referer headers. Additionally, apply proper output escaping when rendering user-supplied data to prevent stored XSS execution.
Fix this in Super Page Cache
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-27968 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-27968 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data