{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-32790 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-32790 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-32790 is a medium-severity SQL injection vulnerability in woocommerce, published on 26 Jul 2021. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-32790 and fix it if it is affected.\n\nWhat it is: CVE-2021-32790 is a medium-severity SQL injection vulnerability in woocommerce, published on 26 Jul 2021. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-32790 in the wild and no public exploit code.\n\nAffected product: woocommerce. 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-2021-32790/ (Markdown: https://insights.sbomify.com/CVE-2021-32790/index.md)","id":"CVE-2021-32790","markdown":"https://insights.sbomify.com/CVE-2021-32790/index.md","name":"CVE-2021-32790","record":{"aliases":["GHSA-7vx5-x39w-q24g"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"WooCommerce plugin","requires_auth":"high_privilege","summary":"Authenticated attackers with admin access or API keys can exploit blind SQL injection in WooCommerce webhook search endpoints to disclose sensitive data via timing attacks.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"woocommerce","vendor":"woocommerce"}],"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":"Woocommerce is an open source eCommerce plugin for WordPress. An SQL injection vulnerability impacts all WooCommerce sites running the WooCommerce plugin between version 3.3.0 and 3.3.6. Malicious actors (already) having admin access, or API keys to the WooCommerce site can exploit vulnerable endpoints of `/wp-json/wc/v3/webhooks`, `/wp-json/wc/v2/webhooks` and other webhook listing API. Read-only SQL queries can be executed using this exploit, while data will not be returned, by carefully crafting `search` parameter information can be disclosed using timing and related attacks. Version 3.3.6 is the earliest version of Woocommerce with a patch for this vulnerability. There are no known workarounds other than upgrading.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Blind SQL Injection possible via Authenticated Web-hook Search API Endpoint","id":"CVE-2021-32790","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2021"},"n_packages":0,"n_references":2,"next":{"headline":"Hardcoded static IV and AAD with a reused key in AES GCM encryption in mod_auth_openidc","id":"CVE-2021-32791"},"packages":[],"prev":{"headline":"Arbitrary SQL (SQL injection) possible via the Store API component.","id":"CVE-2021-32789"},"products":["woocommerce"],"published":"2021-07-26","related":[{"cvss_score":8.8,"headline":"WooCommerce Cross-Site Request Forgery (CSRF)","id":"CVE-2019-20891","kev_date_added":null,"published":"2020-06-19"},{"cvss_score":8.8,"headline":"Code injection in n/a","id":"CVE-2017-18356","kev_date_added":null,"published":"2019-01-15"},{"cvss_score":8.1,"headline":"Path traversal in n/a","id":"CVE-2018-20714","kev_date_added":null,"published":"2019-01-15"},{"cvss_score":6.1,"headline":"WooCommerce \u003c= 9.4.2 - PostMessage-Based Cross-Site Scripting","id":"CVE-2025-5062","kev_date_added":null,"published":"2025-05-22"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2019-9168","kev_date_added":null,"published":"2019-02-26"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2015-2329","kev_date_added":null,"published":"2018-02-08"},{"cvss_score":5.9,"headline":"WordPress Product page shipping calculator for WooCommerce Plugin \u003c= 1.3.25 is vulnerable to Cross Site Scripting (XSS)","id":"CVE-2023-32575","kev_date_added":null,"published":"2023-08-25"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["woocommerce"]},"summary":"Authenticated attackers with admin access or API keys can exploit blind SQL injection in WooCommerce webhook search endpoints to disclose sensitive data via timing attacks.","url":"https://insights.sbomify.com/CVE-2021-32790/"}