WootWordPress extension · Pluginus
CVE-2024-35730
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 · uneditedImproper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in realmag777 Active Products Tables for WooCommerce allows Reflected XSS.This issue affects Active Products Tables for WooCommerce: from n/a through 1.0.6.3.
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 confidenceThis is a reflected cross-site scripting (XSS) vulnerability in the Active Products Tables for WooCommerce plugin by realmag777. The vulnerability allows attackers to inject malicious JavaScript code through unsanitized input that gets reflected back in web pages generated by the plugin, potentially leading to session hijacking or credential theft when users click crafted links.
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
WootWordPress extension
< 1.0.6.4CVSS 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.
-
Locate the installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins. Find 'Active Products Tables for WooCommerce' (also listed as Pluginus Woot). The version number is displayed below the plugin name.Affected if The version shown is lower than 1.0.6.4 (e.g., 1.0.6.3, 1.0.6.2, etc.)
-
Verify the plugin is activeIn WordPress admin > Plugins > Installed Plugins, confirm the plugin has a blue 'Active' link beneath its name. Also check if any pages or shortcodes using the plugin are publicly accessible.Affected if The plugin is active and accessible to visitors on the frontend of the site
-
Identify plugin-generated pagesSearch your site for shortcodes like [woot] or [woot_products_tables] in posts, pages, or widgets. Check if any WooCommerce product table views are publicly accessible via URL.Affected if The plugin shortcodes or tables are in use and publicly visible
-
Inspect HTTP parameters for potential XSS vectorsIf the plugin accepts URL parameters (such as ids, product_id, cat, or similar query strings), test whether unsanitized input in the URL reflects back in the HTML output. Use browser DevTools Network tab to examine responses.Affected if User-supplied parameters from the URL are reflected in the page HTML without encoding
You are affected if the plugin version is below 1.0.6.4 AND the plugin is active with publicly accessible tables or shortcodes that reflect URL parameters in the output.
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 · scoped1.0.6.4
Apply proper output encoding/escaping to all user-supplied input before rendering in HTML context. Sanitize and validate all input parameters using WordPress sanitization functions and implement context-aware escaping based on where the data is output.
1.0.6.4
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find 'Active Products Tables for WooCommerce' (also listed as 'Woot') in the plugin list
- Click 'Update now' if an update is available, or manually upload version 1.0.6.4 of the plugin
- Verify the plugin is updated to version 1.0.6.4
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Woot
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-35730 — 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-35730 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