WordPress security changelog
MEDIUM CVE-2026-5651 Deferred

Askeet conditional-comment bypass permits administrator SQL injection

Askeet through 3.0 passes the sql_query parameter to the askeet_execute_sql_query and askeet_export_all_results AJAX actions. askeet_is_safe_query() strips ordinary block comments before checking for forbidden SQL keywords, but MySQL conditional comments such as /*!UNION*/ remain executable and bypass that filter. An Administrator can append SQL capable of extracting sensitive database information. This 4.9-scored record received deeper review because the underlying primitive is SQL injection; the CNA does not disclose the final SQL execution function.

CVE / CNA score 4.9 CVSS 3.1 · security@wordfence.com
NVD score Pending NVD has not published its own CVSS assessment.
Component
Askeet — Talk to Your WooCommerce Data
Plugin slug
askeet
Affected
<= 3.0
Safe version
> 3.0
Published
Aug 05, 2026
Weakness
CWE-89 — Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

This CVE was published Aug 05, 2026 and is one of 1 known issue for this plugin.

What to do

Update, patch or deactivate.

Update Askeet to a release after 3.0. The authoritative record links a trunk correction but does not identify the first fixed release. Restrict administrative query features to trusted users and review AJAX requests for MySQL conditional comments.

A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

Source record

Technical description

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.

CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N

References

Primary and upstream sources