dbcve.org
Product TableWordPress extension · Woobewoo

CVE-2023-51512

HIGH · 8.8 CVSS v3.1 Published 2024-03-16
Fix available
A fix is available. Upgrade to 1.8.7 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 · unedited
Cross Site Request Forgery (CSRF) vulnerability in WBW Product Table by WBW.This issue affects Product Table by WBW: from n/a through 1.8.6.

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 confidence

Cross-Site Request Forgery (CSRF) vulnerability in the WordPress 'Product Table by WBW' plugin allows attackers to induce authenticated administrators to perform unintended actions, such as modifying plugin settings or table configurations, by tricking them into visiting malicious URLs.

MitigationImplement anti-CSRF nonces (WordPress nonces) on all state-changing operations (admin actions, form submissions, AJAX requests) within the plugin to verify request origin and intent.

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
Product TableWordPress extension
Affected:< 1.8.7

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm plugin installation
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins. Look for 'Product Table by WBW' or 'Woobewoo Product Table' in the list of active or installed plugins.
    Affected if The plugin is not installed or not active, then the vulnerability does not apply.
  2. Identify installed version
    In the plugins list, find the 'Product Table by WBW' plugin and note the version number displayed under the plugin name. Alternatively, check the plugin's main PHP file (usually in wp-content/plugins/product-table-by-wbw/) for the version header in the plugin comment block.
    Affected if The installed version is less than 1.8.7 (for example, 1.8.6, 1.8.5, etc.), then the environment is affected.
  3. Verify missing nonce protection in admin actions
    If using a file manager or FTP, access the plugin directory and examine PHP files that handle admin actions, typically files like admin.php, controller.php, or files in an 'controllers' folder. Search for 'admin_action' or form submission handlers and check if WordPress nonces (wp_verify_nonce, check_admin_referer) are used to validate requests before performing state-changing operations.
    Affected if State-changing admin operations (such as saving settings, updating table configurations, or modifying plugin options) lack nonce verification, confirming the CSRF vulnerability is present and exploitable.

The environment is affected if the Product Table by WBW plugin is installed with a version lower than 1.8.7 and the admin action handlers lack WordPress nonce validation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 1.8.7 or later
Fixed in 1.8.7
Interim mitigation

Implement anti-CSRF nonces (WordPress nonces) on all state-changing operations (admin actions, form submissions, AJAX requests) within the plugin to verify request origin and intent.

Recommended fix High confidence

1.8.7

  1. 1. Back up your WordPress site and database before making any changes
  2. 2. Navigate to the WordPress admin dashboard
  3. 3. Go to Plugins > Installed Plugins
  4. 4. Find 'Product Table by WBW' in the plugin list
  5. 5. If an update is available, click 'Update Now' to upgrade to version 1.8.7
  6. 6. Alternatively, go to Dashboard > Updates and select the plugin to update
  7. 7. Verify the update was successful by checking the plugin version after completion

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Product Table Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,848.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-51512 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-51512 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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