{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-5651 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-5651 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-5651 is a medium-severity SQL injection vulnerability in 2wstechnologies Askeet — Talk to Your WooCommerce Data, published on 5 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-5651 and fix it if it is affected.\n\nWhat it is: CVE-2026-5651 is a medium-severity SQL injection vulnerability in 2wstechnologies Askeet — Talk to Your WooCommerce Data, published on 5 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-5651 in the wild and no public exploit code.\n\nAffected product: 2wstechnologies Askeet — Talk to Your WooCommerce Data. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-5651/ (Markdown: https://insights.sbomify.com/CVE-2026-5651/index.md)","id":"CVE-2026-5651","markdown":"https://insights.sbomify.com/CVE-2026-5651/index.md","name":"CVE-2026-5651","record":{"aliases":["GHSA-w4cg-h4j3-3gf6"],"analysis":{"component_type":"cms_plugin","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"high_privilege","summary":"Authenticated administrators can bypass SQL filters to extract sensitive database information via the sql_query parameter in the Askeet WordPress plugin.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":4.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Askeet \u003c= 3.0 - Authenticated (Administrator+) SQL Injection via 'sql_query' Parameter","id":"CVE-2026-5651","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"Authorization Bypass Through User-Controlled Key in Crafty Controller","id":"CVE-2026-5652"},"packages":[],"prev":{"headline":"code-projects Online Application System for Admission oas.sql sensitive information","id":"CVE-2026-5650"},"products":["Askeet — Talk to Your WooCommerce Data"],"published":"2026-08-05","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-05","vendors":["2wstechnologies"]},"summary":"Authenticated administrators can bypass SQL filters to extract sensitive database information via the sql_query parameter in the Askeet WordPress plugin.","url":"https://insights.sbomify.com/CVE-2026-5651/"}