CVE-2024-4102
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 unauthorized access of data due to a missing capability check on the ajax() function in all versions up to, and including, 2.0.1. This makes it possible for authenticated attackers, with subscriber-level access and above, to perform unauthorized actions like editing pricing tables.
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 has a broken access control vulnerability in its ajax() function, which lacks a capability check. This allows any authenticated user with subscriber-level privileges or higher to access administrative functions and modify pricing tables, even though subscribers should only have read-only access.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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.
-
Confirm Pricing Table plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Pricing Table' or 'pricings-table' in the plugin list. Check if it is activated.Affected if The plugin is installed and activated in WordPress.
-
Identify installed plugin versionClick on the plugin name in the Plugins list to view details, or check the plugin header in /wp-content/plugins/pricing-table/pricing-table.php for the 'Version' field.Affected if The installed version matches or precedes the patched version (compare against the latest version on wordpress.org).
-
Verify ajax endpoint is accessibleCheck if the WordPress site responds to admin-ajax.php?action=pricings_table_ajax or similar pricing table related ajax actions. Test with a low-privileged subscriber account using a tool like curl or Burp.Affected if The ajax endpoint returns a response instead of a 401/403 error when accessed without proper authentication.
-
Inspect ajax() function for capability checkExamine the plugin source code in /wp-content/plugins/pricing-table/ for the ajax() function. Look for current_user_can() or similar capability verification at the function entry point.Affected if The ajax() function contains NO capability check (no current_user_can() call) and processes requests from any authenticated user.
-
Confirm subscriber-level access existsGo to Users > All Users in WordPress admin. Verify there are users with the 'Subscriber' role or any role below Administrator.Affected if Any user with Subscriber role or higher can be authenticated on the site.
If the Pricing Table plugin is installed and its ajax() function can be invoked by any authenticated user without a capability check, the environment is affected by CVE-2024-4102.
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 dataAdd proper capability checks (e.g., current_user_can('manage_options')) to the ajax() function and update to the latest patched version when available. Restrict the endpoint to users with administrative privileges.
- Consultation2.0 h
- Implementation1.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 $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-4102 — 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-4102 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