Security readout for executives and security teams
Plain-English summary
A WordPress WooCommerce plugin can let an unauthenticated visitor manipulate database queries through product search. The main business risk is exposure of sensitive database information from affected online stores. There is no cited evidence of active exploitation or CISA KEV listing in the provided sources.
Executive priority
Treat as a high-priority e-commerce data exposure issue. Prioritize internet-facing stores because exploitation requires no login and targets database confidentiality. Patch or disable affected plugin instances after confirming vendor guidance.
Technical view
CVE-2026-2232 is a time-based SQL injection in Product Table and List Builder for WooCommerce Lite through version 4.6.2. The vulnerable input is the search parameter, caused by insufficient escaping and query preparation. CVSS 3.1 is 7.5, network exploitable, low complexity, no privileges or user interaction required, with high confidentiality impact.
Likely exposure
Public WordPress sites using Product Table and List Builder for WooCommerce Lite version 4.6.2 or earlier are the likely exposure. Risk is highest where product table search is reachable by unauthenticated visitors.
Exploitation context
The sources describe unauthenticated, remote time-based SQL injection that may extract database information. The provided bundle does not show active exploitation, public exploit use, or KEV inclusion.
Researcher notes
Relevant code references are in search.php around the cited lines, with WordPress Trac changeset 3457877 linked as a code change. The bundle does not provide a named fixed release, so avoid assuming a safe version without vendor confirmation.
Mitigation direction
- Identify all WordPress sites using the affected WooCommerce Lite plugin.
- Update the plugin according to vendor or WordPress plugin repository guidance.
- If no safe update is available, disable the plugin until guidance is confirmed.
- Restrict unnecessary public access to affected product search functionality where feasible.
- Review web application firewall rules for SQL injection detection coverage.
Validation and detection
- Inventory plugin name and version across WordPress estates.
- Confirm whether any installation runs version 4.6.2 or earlier.
- Check vendor changelog or WordPress Trac changeset 3457877 for remediation details.
- Review web logs for unusual requests to product search parameters.
- Validate remediation in staging before production rollout.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-2232 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N3.93.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/f2891f3d-9081-4a9f-8408-2373ce1d0306?source=cveCVE reference
- https://plugins.trac.wordpress.org/browser/wc-product-table-lite/trunk/search.php#L549CVE reference
- https://plugins.trac.wordpress.org/browser/wc-product-table-lite/tags/4.6.2/search.php#L549CVE reference
- https://plugins.trac.wordpress.org/changeset/3457877/CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.