Askeet <= 3.0 - Authenticated (Administrator+) SQL Injection via 'sql_query' Parameter
Strategic Overview
- Status
- Patched in 3.1
- Affected Plugin
- Askeet — Talk to Your WooCommerce Data
- Affected Version
<= 3.0- CVSS
- 4.9Medium
- Weakness type
- CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
- CVE
CVE-2026-5651
At a glance
CVE-2026-5651 is a medium-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the Askeet WordPress plugin, affecting versions <= 3.0. It carries a CVSS score of 4.9 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires an authenticated account at Administrator level or above. The issue is fixed in version 3.1; sites on affected versions should update now. Disclosed August 2026, reported by Régis SENET.
Vulnerability Overview
The Askeet plugin for WordPress is vulnerable to SQL Injection via the 'sql_query' parameter in multiple AJAX actions (askeet_execute_sql_query, askeet_export_all_results) in all versions up to, and including, 3.0. This is due to the askeet_is_safe_query() filter being bypassable using MySQL conditional comments (e.g., /*!UNION*/). The filter strips regular block comments before checking for forbidden SQL keywords, but MySQL interprets conditional comments as executable code. This makes it possible for authenticated attackers, with Administrator-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on confidentiality.
CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Askeet <= 3.0 carries this weakness at sql_query, and reaching it takes an account at Administrator level or above. SQL injection happens when request data is concatenated into a query instead of being bound as a parameter, letting an attacker change the structure of the statement rather than just its values.
A working injection can read any table the database user can see, which on a WordPress install means user records, password hashes and session or API secrets stored in options. For Askeet the fix is 3.1: builds <= 3.0 are affected, anything from 3.1 onward is not.
Remediation
Update to version 3.1, or a newer patched version
How WordSec helps
An attacker needs Administrator access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Askeet 3.1 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C