CVE-2024-10959
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 The Active Products Tables for WooCommerce. Use constructor to create tables plugin for WordPress is vulnerable to arbitrary shortcode execution via woot_get_smth AJAX action in all versions up to, and including, 1.0.6.5. This is due to the software allowing users to execute an action that does not properly validate a value before running do_shortcode. This makes it possible for unauthenticated attackers to execute arbitrary shortcodes.
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 Active Products Tables for WooCommerce plugin has an unauthenticated arbitrary shortcode execution vulnerability in the woot_get_smth AJAX action. The plugin fails to properly validate input before passing it to do_shortcode(), allowing attackers to execute any registered WordPress shortcode without authentication.
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
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
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 the plugin is installedCheck the WordPress plugins directory (wp-content/plugins/) for folders containing 'active-products-tables-for-woocommerce' or 'woot' in the name. Look for a main plugin file containing the plugin name and version header.Affected if The plugin folder exists in the WordPress installation
-
Determine the installed plugin versionOpen the main plugin PHP file (usually in the plugin root folder) and locate the Version header in the plugin comment block, or check the version in readme.txt.Affected if The installed version is older than any patched version released for this CVE
-
Confirm WooCommerce is activeIn WordPress admin, go to Plugins and verify WooCommerce is active, or check wp_options table for active_plugins option.Affected if WooCommerce is active and the vulnerable plugin is installed
-
Test AJAX endpoint accessibilitySend a POST request to /wp-admin/admin-ajax.php with action=woot_get_smth and a test shortcode parameter (such as parameter name used by the plugin). For unauthenticated access, do not include any authentication cookies.Affected if The AJAX endpoint responds without requiring authentication (401 or 403 not returned)
-
Verify shortcode execution is possibleSend a POST to admin-ajax.php with action=woot_get_smth containing a harmless registered shortcode (e.g., one known to exist like [site_url] or a simple text shortcode) and observe if do_shortcode output appears in the response.Affected if The response contains executed shortcode output, indicating the vulnerability is present
A user is affected if the Active Products Tables for WooCommerce plugin is installed, WooCommerce is active, and the woot_get_smth AJAX action is accessible without authentication, allowing arbitrary shortcode execution.
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 plugin to a patched version once available. If no patch exists, disable the plugin or restrict access to the vulnerable AJAX endpoint via server-side configuration until a fix is released.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-10959 — 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-10959 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