CVE-2024-10813
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 Product Table for WooCommerce by CodeAstrology (wooproducttable.com) plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 3.5.1 via the var_dump_table parameter. This makes it possible for unauthenticated attackers var data.
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 Product Table for WooCommerce plugin versions up to 3.5.1 contains an unauthenticated information disclosure vulnerability via the var_dump_table parameter. This parameter, likely a debug feature, allows remote attackers to dump variable data including potentially sensitive information such as database contents, configuration details, or user data without authentication.
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< 3.5.2CVSS 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 the plugin is installedCheck your WordPress plugins directory (wp-content/plugins/) for a folder named 'woo-product-table' or similar, or view the installed plugins list in WordPress admin under Plugins > Installed PluginsAffected if The plugin 'Product Table for WooCommerce' or 'Woo Product Table' by Codeastrology is present
-
Identify the installed versionOpen the main plugin PHP file (usually woo-product-table.php or similar in the plugin folder) and look for the 'Version' header in the plugin comments, or check the WordPress plugins admin page for the version numberAffected if The installed version is 3.5.1 or lower (anything below 3.5.2)
-
Test for unauthenticated var_dump_table accessSend a GET request to your site with the parameter 'var_dump_table' present (e.g., yoursite.com/?var_dump_table=1 or any page with this parameter), observe if the response contains PHP variable dumps, database information, or serialized dataAffected if The parameter is accepted and returns PHP var_dump output, configuration details, or any sensitive data without requiring login
-
Check server access logs for var_dump_table requestsReview your web server access logs (Apache/Nginx) for any GET requests containing 'var_dump_table' parameter from external IPs, especially unauthenticated requestsAffected if Unauthenticated requests to endpoints with var_dump_table parameter are logged and returning data
You are affected if the Product Table for WooCommerce plugin version is below 3.5.2 AND the var_dump_table parameter is accessible without authentication, returning sensitive debug information.
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 · scoped3.5.2
Update the plugin to the latest version once available, or implement a WAF rule to block requests containing the var_dump_table parameter until an update can be applied. If no patch is forthcoming, consider alternative product table solutions.
3.5.2
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Locate the 'Woo Product Table' (Product Table for WooCommerce by CodeAstrology) plugin
- If the plugin shows an update available, click 'Update Now' to update to version 3.5.2 or higher
- Alternatively, download version 3.5.2 from the WordPress plugin repository and upload it manually via Plugins > Add New > Upload Plugin
- Verify the updated version number reflects 3.5.2 or later after updating
Generated from the published advisory — verify against the referenced sources before acting.
- 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-10813 — 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-10813 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