Askeet — Talk To Your Woocommerce Data
Approved changes feed: RSS · Atom
cpe:2.3:a:2wstechnologies:askeet_—_talk_to_your_woocommerce_data:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | 2Wstechnologies (1adcb202-a167-5e86-bbd6-0009509bcae0) |
|---|---|
| Product | Askeet — Talk To Your Woocommerce Data (8edfb419-7a8a-5282-86f6-1646db2904d2) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-5651 |
vulnerable | 2026-09-16 04:33:52.343688 |
Askeet <= 3.0 - Authenticated (Administrator+) SQL Injection via 'sql_query' Parameter
MEDIUM (4.9)
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.
Published: 2026-08-05T06:38:00.167Z
Updated: 2026-08-05T14:15:49.483Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.