Skip to main content
Vulnerability Database/CVE-2026-92766

CVE-2026-92766: Vitepos WooCommerce POS SQL Injection

CVE-2026-92766 is a SQL injection vulnerability in the Vitepos Point of Sale plugin for WooCommerce that allows unauthenticated attackers to extract sensitive database information. This article covers technical details, affected versions, security impact, and mitigation strategies.

Published:

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-92766 Overview

CVE-2026-92766 is a SQL injection vulnerability in the Vitepos – Point of Sale (POS) for WooCommerce plugin for WordPress. The flaw affects all versions up to and including 3.5.1. It stems from insufficient escaping of the src_by parameter and inadequate query preparation in the plugin's vendor list REST endpoint. Unauthenticated attackers, or authenticated users holding any POS role such as vtpos-cashier, can append arbitrary SQL to existing queries. Successful exploitation enables extraction of sensitive data from the WordPress database.

Critical Impact

Attackers can read arbitrary database contents, including WordPress user credentials, session tokens, and customer records stored by WooCommerce.

Affected Products

  • Vitepos – Point of Sale (POS) for WooCommerce plugin (vitepos-lite) for WordPress
  • All versions up to and including 3.5.1
  • WordPress sites exposing the /vitepos/v1/vendor/list REST route

Discovery Timeline

  • 2026-10-16 - CVE-2026-92766 published to the National Vulnerability Database (NVD)
  • 2026-10-16 - Last updated in NVD database

Technical Details for CVE-2026-92766

Vulnerability Analysis

The vulnerability resides in the Vitepos Lite vendor API handler at vitepos_lite/api/v1/class-pos-vendor-api.php. The src_by request parameter flows into the plugin's base model and query builder components without parameterized binding. Because the upstream SQL assembly in class-basemodel.php and class-querybuilder.php concatenates the value directly, attackers can inject additional SQL clauses into the generated query. The affected REST route /vitepos/v1/vendor/list enforces a permission callback that only verifies a POS role assignment. Unauthenticated requests and low-privilege POS cashiers can reach the vulnerable code path. This issue is classified under CWE-89: Improper Neutralization of Special Elements used in an SQL Command.

Root Cause

The root cause is missing input escaping combined with the absence of wpdb::prepare() for the SQL statement that consumes src_by. The query builder trusts the sorting field supplied by the client and composes it into the final SQL string. No allow-list validation restricts src_by to known column names.

Attack Vector

An attacker sends a crafted HTTP request to the /vitepos/v1/vendor/list endpoint containing a malicious src_by value. The payload closes the existing clause and appends a UNION SELECT or similar statement to exfiltrate records. Exploitation does not require authentication, user interaction, or elevated privileges. See the Wordfence Vulnerability Analysis and the vulnerable Vitepos Lite Vendor API Code for the handler definition and the class-querybuilder.php sink.

Detection Methods for CVE-2026-92766

Indicators of Compromise

  • HTTP requests to /wp-json/vitepos/v1/vendor/list containing SQL metacharacters in the src_by query parameter, such as single quotes, parentheses, UNION, SELECT, SLEEP, or -- sequences.
  • Unexpected or anomalous responses from the vendor list endpoint containing columns outside the standard vendor schema.
  • Database error messages or long response times from the vendor list REST route, consistent with error-based or time-based SQL injection probing.

Detection Strategies

  • Enable WordPress REST API request logging and alert on non-alphanumeric values submitted to the src_by parameter.
  • Deploy Web Application Firewall (WAF) signatures that identify SQL keywords inside query parameters sent to /wp-json/vitepos/* routes.
  • Review authentication logs for POS role accounts (for example vtpos-cashier) issuing requests to vendor endpoints outside normal operational patterns.

Monitoring Recommendations

  • Centralize WordPress and web server access logs for correlation and retroactive hunting across REST API traffic.
  • Monitor MySQL general or slow query logs for queries referencing vendor tables containing injected UNION or INFORMATION_SCHEMA references.
  • Track plugin version inventory across WordPress sites to identify instances still running Vitepos 3.5.1 or earlier.

How to Mitigate CVE-2026-92766

Immediate Actions Required

  • Upgrade the Vitepos – Point of Sale (POS) for WooCommerce plugin to a version later than 3.5.1 once released by the vendor.
  • Restrict external access to /wp-json/vitepos/v1/vendor/list using WAF rules or server-level access controls until a patch is applied.
  • Audit all accounts assigned POS roles such as vtpos-cashier and remove unnecessary role grants.
  • Rotate WordPress administrator passwords and secret keys if the vendor list endpoint has been reachable from the internet.

Patch Information

A source code change is tracked in the WordPress Vitepos Lite Changeset. Site administrators should install the fixed release from the WordPress plugin repository and verify the installed version is greater than 3.5.1.

Workarounds

  • Deactivate the Vitepos plugin on production sites where the POS functionality is not actively used.
  • Add a WAF rule to block requests to /wp-json/vitepos/v1/vendor/list where the src_by parameter contains characters outside [A-Za-z0-9_].
  • Restrict the vendor list REST endpoint to trusted IP ranges associated with physical POS terminals.
bash
# Example ModSecurity rule to block SQL metacharacters in the src_by parameter
SecRule REQUEST_URI "@contains /wp-json/vitepos/v1/vendor/list" \
    "id:1092766,phase:2,deny,status:403,\
     chain,msg:'CVE-2026-92766 Vitepos SQLi attempt'"
    SecRule ARGS:src_by "@rx [^A-Za-z0-9_]" \
        "t:none,t:urlDecodeUni"

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

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.