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.
References6
- plugins.trac.wordpress.org/browser/askeet/tags/2.5/askeet.php#L…
- plugins.trac.wordpress.org/browser/askeet/tags/2.5/askeet.php#L…
- plugins.trac.wordpress.org/browser/askeet/trunk/askeet.php#L767
- plugins.trac.wordpress.org/changeset?new=3525593%40askeet%2Ftru…
- wordpress.org/plugins/askeet/
- www.wordfence.com/threat-intel/vulnerabilities/id/b95af878-f324…
Metrics
- CVSS 3.1
-
4.9
MEDIUM
Score source: CNA
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N - EPSS — exploit probability
- 1% percentile: 44 · as of 13 November 2026
- CWE
- CWE-89
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.