Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-109414 Overview
The Vitepos – Point of Sale (POS) for WooCommerce plugin for WordPress contains a blind SQL injection vulnerability in the src_by[].val.start and src_by[].val.end parameters when the bt (BETWEEN) operator is used. The flaw affects all versions up to and including 3.6.1. Authenticated attackers with vendor-level access or above can append arbitrary SQL to existing queries and extract sensitive database contents. This issue represents an incomplete fix for an earlier SQL injection patched in version 3.6.0, which addressed the gt, lt, le, and ge operators but left the bt branch unprotected. The weakness maps to CWE-89: Improper Neutralization of Special Elements used in an SQL Command.
Critical Impact
Authenticated vendors can exfiltrate arbitrary database contents, including customer records, order data, and WordPress user credentials stored in wp_users.
Affected Products
- Vitepos – Point of Sale (POS) for WooCommerce (vitepos-lite) versions ≤ 3.6.1
- WordPress installations exposing the Vitepos REST API endpoints (class-pos-outlet-api.php, class-pos-purchase-api.php, class-pos-vendor-api.php)
- Deployments relying on the shared query builder in class-basemodel.php and class-api-base.php
Discovery Timeline
- 2026-10-16 - CVE-2026-109414 published to the National Vulnerability Database
- 2026-10-16 - Last updated in NVD database
Technical Details for CVE-2026-109414
Vulnerability Analysis
The vulnerability resides in the Vitepos search filter handler, which accepts a src_by[] array describing columns, operators, and values. When the operator is bt, the handler constructs a BETWEEN clause from val.start and val.end without passing the values through $wpdb->prepare() or an equivalent escaping routine. The earlier 3.6.0 patch sanitized comparison operators such as gt, lt, ge, and le, but the branch handling bt reuses the raw user input directly in the final SQL string.
Exploitation requires an authenticated account with vendor-level privileges, which lowers reach but does not eliminate risk in multi-tenant storefronts that onboard external vendors. A successful attacker can issue blind, boolean-based, or time-based payloads against the WordPress database, exfiltrating password hashes, API keys, session tokens, and WooCommerce order details.
Root Cause
The affected query builder in vendor/appsbd-wp/appsbd-lite/appsbd_lite/v6/core/class-basemodel.php concatenates the BETWEEN operands into the generated SQL rather than binding them as parameters. Because the sanitization logic added in 3.6.0 branched only on scalar operators, the array-based range operator inherited no protection, leaving the user-controlled start and end values interpreted as SQL.
Attack Vector
An authenticated vendor sends a REST request to a Vitepos API endpoint (for example, outlet, purchase, or vendor search routes) containing a src_by array where the operator is bt. The attacker places SQL payloads inside val.start or val.end. The server concatenates these values into the WHERE clause, enabling blind extraction techniques such as boolean inference or time-delay queries using SLEEP() or conditional subqueries. See the Wordfence Vulnerability Analysis and the WordPress VitePOS API Base Library Code for the vulnerable code path.
Detection Methods for CVE-2026-109414
Indicators of Compromise
- Requests to Vitepos REST routes containing src_by parameters with operator=bt and SQL metacharacters such as ', --, UNION, or SLEEP( in val.start or val.end
- Unusually long response times on vendor, outlet, or purchase search endpoints consistent with time-based blind injection
- Database error entries referencing BETWEEN syntax from WordPress PHP logs tied to Vitepos handlers
- Spikes in authenticated API calls from vendor-role accounts enumerating product, user, or order tables
Detection Strategies
- Inspect HTTP request bodies and query strings for src_by[...][operator]=bt combined with non-numeric or non-date values in val.start and val.end
- Enable WordPress query logging or a Web Application Firewall rule targeting SQL keywords within Vitepos REST paths under /wp-json/vitepos/
- Correlate vendor-role authentication events with REST API calls to Vitepos endpoints to identify low-privilege accounts probing search filters
Monitoring Recommendations
- Monitor WooCommerce database users for unexpected SELECT activity against wp_users, wp_usermeta, and WooCommerce order tables outside normal POS workflows
- Alert on new vendor account creation followed by immediate access to Vitepos search endpoints
- Track plugin version inventory to confirm all WordPress sites run a patched Vitepos release above 3.6.1
How to Mitigate CVE-2026-109414
Immediate Actions Required
- Update the Vitepos – Point of Sale (POS) for WooCommerce plugin to a release above 3.6.1 that fully sanitizes the bt operator branch
- Audit vendor-role accounts and remove any that are inactive, untrusted, or recently created from unknown sources
- Rotate WordPress administrator passwords, WooCommerce API keys, and any secrets stored in the database if compromise is suspected
Patch Information
Review the WordPress VitePOS Revision Changeset for the fix that extends sanitization to the BETWEEN operator branch inside class-basemodel.php. Apply the vendor-released version through the WordPress plugin updater and verify the active version using wp plugin list or the admin Plugins page.
Workarounds
- Deploy a WAF rule that blocks requests to Vitepos REST endpoints when src_by[...][operator] equals bt and the paired val.start or val.end contains SQL metacharacters
- Temporarily disable the Vitepos plugin on sites that cannot update immediately, especially storefronts that grant vendor roles to third parties
- Restrict access to /wp-json/vitepos/ routes to trusted IP ranges using web server access controls until patching completes
# Example nginx rule to block the vulnerable operator pattern
location ~* /wp-json/vitepos/ {
if ($args ~* "src_by\[.*\]\[operator\]=bt") {
return 403;
}
}
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

