CVE-2024-4100
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 Pricing Table plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.0.1. This is due to missing or incorrect nonce validation on the ajax() function. This makes it possible for unauthenticated attackers to perform a variety of actions related to managing pricing tables 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 Pricing Table WordPress plugin fails to validate nonces in its ajax() function, allowing unauthenticated attackers to forge requests that manipulate pricing tables. An attacker tricks a logged-in administrator into clicking a malicious link, causing the admin's browser to execute unauthorized actions via the vulnerable ajax endpoint.
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
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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.
-
Identify if Pricing Table plugin is installedCheck the WordPress plugins directory (wp-content/plugins/) for a folder named 'pricing-table' or 'pricing-table-by' and inspect the main plugin file's header comment for the version numberAffected if The plugin is found and the version is below 2.0.2
-
Compare installed version to fixed releaseLocate the version number in the plugin's main PHP file (usually in the plugin header comment) or in readme.txt, then compare against 2.0.2Affected if The installed version is lower than 2.0.2 or the version cannot be determined
-
Verify ajax endpoint is accessibleCheck if the WordPress site has admin-ajax.php exposed (standard in WP) and attempt to identify the plugin's ajax action hooks by examining the plugin code for add_action('wp_ajax_...') or do_action callsAffected if The plugin registers ajax actions without nonce validation checks
-
Inspect ajax function for nonce validationExamine the plugin's ajax handler function (search for function ajax() or wp_ajax_ hooks) and verify if it contains nonce verification calls such as check_ajax_referer(), wp_verify_nonce(), or wp_nonce_field() before processing requestsAffected if The ajax function lacks nonce verification logic (check_ajax_referer or wp_verify_nonce calls)
-
Assess admin exposure to CSRF riskDetermine if administrators actively use the WordPress admin dashboard, as exploitation requires tricking a logged-in admin into clicking a malicious linkAffected if Administrators use the admin panel and the plugin version is vulnerable
A user is affected if the Pricing Table WordPress plugin is installed with a version lower than 2.0.2 and the ajax endpoint is accessible without proper nonce validation checks.
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 dataUpdate the Pricing Table plugin to version 2.0.2 or later, which should include proper nonce validation. Until then, advise administrators to avoid clicking untrusted links.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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 $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-4100 — 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-4100 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