dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-2232

HIGH · 7.5 CVSS v3.1 Published 2026-02-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
The Product Table and List Builder for WooCommerce Lite plugin for WordPress is vulnerable to time-based SQL Injection via the 'search' parameter in all versions up to, and including, 4.6.2 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

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 confidence

The Product Table and List Builder for WooCommerce Lite WordPress plugin versions up to 4.6.2 contain a time-based SQL injection vulnerability in the 'search' parameter. The flaw stems from insufficient escaping of user-supplied input combined with lack of prepared statements in the underlying SQL query, allowing unauthenticated attackers to inject malicious SQL queries.

MitigationUpdate the plugin to version 4.6.3 or later. If no update is available, disable the plugin immediately or implement a WAF rule to block SQL injection attempts targeting the 'search' parameter.

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

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

  1. Check the installed plugin version
    Access WordPress admin panel, navigate to Plugins > Installed Plugins, locate 'Product Table and List Builder for WooCommerce Lite' and read the version number displayed below the plugin name. Alternatively, inspect the main plugin file (such as product-table-list-builder-for-woocommerce-lite.php) and locate the 'Version' header in the plugin comment block.
    Affected if the displayed version is 4.6.2 or lower (any version up to and including 4.6.2)
  2. Verify WooCommerce is active
    In the WordPress admin panel, confirm WooCommerce is installed and active. The vulnerable plugin requires WooCommerce to be present for its functionality to be loaded.
    Affected if WooCommerce is active and the plugin version is 4.6.2 or lower
  3. Confirm the search feature is exposed
    The plugin exposes a product search functionality that utilizes a 'search' parameter in HTTP requests. Identify if this endpoint is publicly accessible by locating the product table shortcode or widget implementation used on the site.
    Affected if the product search feature is accessible to unauthenticated users and the plugin version is 4.6.2 or lower
  4. Review access logs for the search parameter
    Examine web server access logs (Apache, Nginx, or WAF logs) for incoming requests that include a 'search' parameter. Look for unusual patterns such as SQL keywords (SELECT, UNION, SLEEP, BENCHMARK) or special characters (quotes, dashes, parentheses) appended to typical search values.
    Affected if the plugin version is 4.6.2 or lower and any suspicious 'search' parameter requests are found in logs

A user is affected if the Product Table and List Builder for WooCommerce Lite plugin version is 4.6.2 or earlier and the product search functionality is enabled on the site.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to version 4.6.3 or later. If no update is available, disable the plugin immediately or implement a WAF rule to block SQL injection attempts targeting the 'search' parameter.

Recommended fix Moderate confidence

Latest version available on WordPress.org (check plugins.trac.wordpress.org for version newer than 4.6.2)

  1. Check the WordPress plugin repository (plugins.trac.wordpress.org) for the latest version of 'Product Table and List Builder for WooCommerce Lite'
  2. Navigate to Plugins > Installed Plugins in WordPress admin
  3. Locate 'Product Table and List Builder for WooCommerce Lite'
  4. If a newer version than 4.6.2 is available, click 'Update Now'
  5. After updating, verify the plugin functions correctly on your site
  6. Consider reviewing your web server logs for any signs of exploitation attempts targeting the 'search' parameter

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-2232 — 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-2026-2232 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