CVE-2024-11336
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 · uneditedThe Clickbank WordPress Plugin (Storefront) plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.7. This is due to missing or incorrect nonce validation via the cs_menu page. This makes it possible for unauthenticated attackers to update settings and inject malicious web scripts via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
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 · high confidenceThe Clickbank WordPress Storefront plugin versions up to 1.7 lacks proper nonce validation on the cs_menu page, allowing unauthenticated attackers to forge administrative requests that can modify plugin settings and inject malicious JavaScript via Cross-Site Request Forgery.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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 plugin is installedIn WordPress admin, go to Plugins > Instored Plugins and look for 'Clickbank WordPress Storefront' or check the plugin directory /wp-content/plugins/ for a clickbank-related folderAffected if The plugin is installed
-
Check installed versionIn WordPress admin Plugins page, click 'View Details' on the Clickbank Storefront plugin to see the version number, or inspect the main plugin file headerAffected if Version is 1.7 or lower
-
Identify cs_menu admin page accessibilityCheck if the plugin registers a menu page with slug or hook name containing 'cs_menu' by examining plugin files or accessing /wp-admin/admin.php?page=cs_menu if it existsAffected if The cs_menu admin page is registered and accessible to administrators
-
Verify settings modification vectorReview the plugin code for form handlers on the cs_menu page that process settings updates without wp_nonce_field or check_admin_referer callsAffected if Settings forms on cs_menu lack nonce validation logic
User is affected if the Clickbank WordPress Storefront plugin version 1.7 or lower is installed and the cs_menu admin page processes settings without nonce verification.
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.
dbcve · scopedUpdate the plugin to a patched version beyond 1.7. If no update is available, implement proper nonce verification on all form actions and admin page hooks in the cs_menu functionality.
Version 1.8 or later
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Locate the 'Clickbank WordPress Plugin (Storefront)' plugin
- Update the plugin to the latest available version (version 1.8 or higher)
Generated from the published advisory — verify against the referenced sources before acting.
- 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-11336 — 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-11336 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