Skip to content
Laskyr

Plugins · askeet · data as of 2026-11-04

Is Askeet safe? Known vulnerabilities and latest version

No known unpatched vulnerabilities in the latest version (4.0.0)

As of 2026-11-04. 1 issue is on record for older versions; version 3.1 or newer fixes all of them that state a fix.

Latest version
4.0.0
Last updated
2026-08-06
Active installs
fewer than 10
Known issues on record
1
Unpatched in latest
0
Tested up to WP
6.9.11

The AI analyst for your WooCommerce store. Ask any question in plain language — get answers, charts, and recommendations in 5 seconds. — by 2wstechnologies

What to do

  1. Update to the latest version (4.0.0). Anything older than 3.1 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
  2. If you cannot update right away, deactivate it until you can.
  3. Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
  4. If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.

With WP-CLI: wp plugin get askeet --field=version shows what you run; wp plugin update askeet updates it.

Check your version

Known vulnerabilities

1 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.

medium 4.9 CVE-2026-5651 · published 2026-08-05

SQL injection in Askeet (3.0 and older)

Affected
3.0 and older
Fixed in
3.1 *
Access needed (per CVSS)
Needs an admin-level account
Range from
CVE record (the advisory publisher) · score by Wordfence
Details from the advisory

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.

NVD CVE-2026-5651Wordfence advisoryCode change (fix)wordpress.orgPlugin source

Recent activity

Browse vulnerabilities

Where this data comes from

Badge for your site or docs (states facts with a date, not a verdict):
Askeet vulnerability status badge
<a href="https://laskyr.com/plugins/askeet"><img src="https://laskyr.com/plugins/askeet/badge.svg" alt="Askeet vulnerability status"></a>

← Check another plugin · Free hacked-site scan

First hour checklist

If the site was just hacked, read the emergency kit before you delete files. The page is free. Email is optional.

Read the emergency kit