Woocommerce Product Table LiteWordPress extension · Wcproducttable
CVE-2023-47519
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in WC Product Table WooCommerce Product Table Lite.This issue affects WooCommerce Product Table Lite: from n/a through 2.6.2.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in WooCommerce Product Table Lite plugin allows attackers to potentially force authenticated administrators to perform unintended actions (such as modifying product table settings) by tricking them into visiting malicious URLs. The plugin lacks proper CSRF token validation on state-changing requests.
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
Woocommerce Product Table LiteWordPress extension
<= 2.6.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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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 plugin is installedCheck your WordPress plugins directory or WordPress admin panel under Plugins > Installed Plugins for 'WooCommerce Product Table Lite' or 'Wcproducttable'Affected if Plugin is present in the WordPress installation
-
Check installed versionIn WordPress admin, go to Plugins > Installed Plugins and look for the version number displayed under the plugin name, or check the plugin header in wp-content/plugins/wc-product-table-lite/readme.txtAffected if Version number is 2.6.2 or lower
-
Identify state-changing endpointsReview the plugin PHP files (especially in includes/ or admin/ folders) for AJAX handlers (wp_ajax_* hooks) and form processing code that modify data (create/update/delete products, change settings)Affected if State-changing AJAX actions or form handlers exist in the plugin without nonce verification
-
Check for missing CSRF tokensSearch plugin source code for 'wp_nonce_field', 'wp_verify_nonce', 'check_admin_referer', or 'check_ajax_referer' functions. Examine forms that submit to admin-post.php, AJAX endpoints, and settings pagesAffected if Forms or AJAX actions that modify data lack nonce verification code (the functions above are absent or not called before processing)
-
Review Referer/Origin header validationSearch plugin code for $_SERVER['HTTP_REFERER'] or $_SERVER['HTTP_ORIGIN'] validation checks on POST requestsAffected if POST requests that change state do not validate the Referer or Origin header
User is affected if WooCommerce Product Table Lite version 2.6.2 or lower is installed AND the plugin contains state-changing forms or AJAX actions without CSRF token (nonce) validation.
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 to the latest version of WooCommerce Product Table Lite when available. Until then, implement anti-CSRF tokens (nonces) on all state-changing forms and AJAX actions within the plugin, and verify the Referer or Origin header on POST requests.
Fix this in Woocommerce Product Table Lite
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-47519 — 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-2023-47519 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