CVE-2026-5651
Received Received - Intake

SQL Injection in Askeet WordPress Plugin

Publication date: 2026-08-05

Last updated on: 2026-08-05

Assigner: Wordfence

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-05
Last Modified
2026-08-05
Generated
2026-08-05
AI Q&A
2026-08-05
EPSS Evaluated
N/A
NVD
CVE-2026-5651
EUVD
EUVD-2026-53183

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
askeet askeet to 3.0 (inc)
askeet askeet 3.1

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-89 The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

The Askeet WordPress plugin has a SQL Injection vulnerability due to a flawed security check in the askeet_is_safe_query() function. The filter strips regular comments but fails to block MySQL conditional comments like /*!UNION*/, allowing authenticated attackers with admin access to bypass security and inject malicious SQL queries.

Detection Guidance

To detect this vulnerability, inspect WordPress sites using the Askeet plugin versions up to 3.0 for suspicious SQL queries in the askeet_execute_sql_query and askeet_export_all_results AJAX actions. Check for conditional comments like /*!UNION*/ in logged queries. Use WordPress debugging tools or query logs to monitor for unauthorized SQL execution attempts.

Impact Analysis

An authenticated attacker with Administrator-level access or higher could exploit this to extract sensitive data from the WordPress database, such as customer, order, or product information. The vulnerability enables additional SQL queries to be appended to existing ones.

Compliance Impact

This vulnerability could potentially impact compliance with GDPR and HIPAA by allowing unauthorized access to sensitive data stored in the WordPress database. Exploitation may lead to exposure of personal or health-related information, violating data protection requirements under these regulations.

Mitigation Strategies

Immediately update the Askeet plugin to version 3.1 or later. If updating is not possible, disable the plugin until the update is applied. Review user roles with Administrator access and limit permissions where possible. Monitor database queries for unusual activity.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-5651. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart