{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-0651 exists.","fix":"No fix has been published for CVE-2022-0651 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-0651 is a critical SQL injection vulnerability in WP Statistics, published on 24 Feb 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-0651 and fix it if it is affected.\n\nWhat it is: CVE-2022-0651 is a critical SQL injection vulnerability in WP Statistics, published on 24 Feb 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-0651 exists.\n\nAffected product: WP Statistics. 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-2022-0651/ (Markdown: https://insights.sbomify.com/CVE-2022-0651/index.md)","id":"CVE-2022-0651","markdown":"https://insights.sbomify.com/CVE-2022-0651/index.md","name":"CVE-2022-0651","record":{"aliases":["GHSA-hx7h-9675-wcgc"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can inject SQL queries via the current_page_type parameter to obtain sensitive information from the database.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"wp_statistics","vendor":"veronalabs"}],"cvss":{"score":9.8,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"The WP Statistics WordPress plugin is vulnerable to SQL Injection due to insufficient escaping and parameterization of the current_page_type parameter found in the ~/includes/class-wp-statistics-hits.php file which allows attackers without authentication to inject arbitrary SQL queries to obtain sensitive information, in versions up to and including 13.1.5.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":1,"refs":[{"date":null,"kind":"nuclei","ref":"http/cves/2022/CVE-2022-0651.yaml","stars":null,"title":"WordPress Plugin WP Statistics \u003c= 13.1.5 - SQL Injection"}],"tier":"weaponised"},"has_fix":null,"headline":"WP Statistics \u003c= 13.1.5 Unauthenticated Blind SQL Injection via current_page_type","id":"CVE-2022-0651","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2022"},"n_packages":0,"n_references":3,"next":{"headline":"Information disclosure in Sophos UTM","id":"CVE-2022-0652"},"packages":[],"prev":{"headline":"Memory corruption in TL-WR940N","id":"CVE-2022-0650"},"products":["WP Statistics"],"published":"2022-02-24","related":[{"cvss_score":9.9,"headline":"WordPress WP Statistics Plugin \u003c= 13.2.10 is vulnerable to SQL Injection","id":"CVE-2022-38074","kev_date_added":null,"published":"2023-03-13"},{"cvss_score":9.8,"headline":"WP Statistics \u003c= 13.1.5 Unauthenticated Blind SQL Injection via current_page_id","id":"CVE-2022-25148","kev_date_added":null,"published":"2022-02-24"},{"cvss_score":9.8,"headline":"WP Statistics \u003c= 13.1.5 Unauthenticated Blind SQL Injection via IP","id":"CVE-2022-25149","kev_date_added":null,"published":"2022-02-24"},{"cvss_score":9.8,"headline":"WP Statistics \u003c= 13.1.4 Unauthenticated Blind SQL Injection via exclusion_reason","id":"CVE-2022-0513","kev_date_added":null,"published":"2022-02-16"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2017-18515","kev_date_added":null,"published":"2019-08-14"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2019-13275","kev_date_added":null,"published":"2019-07-04"}],"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)"},{"class":"attribution","licence":"MIT","name":"Nuclei templates"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-01-31","vendors":["WP Statistics"]},"summary":"Unauthenticated attackers can inject SQL queries via the current_page_type parameter to obtain sensitive information from the database.","url":"https://insights.sbomify.com/CVE-2022-0651/"}