{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-0787 exists.","fix":"No fix has been published for CVE-2022-0787 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-0787 is a critical SQL injection vulnerability in Unknown Limit Login Attempts (Spam Protection), published on 28 Mar 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-0787 and fix it if it is affected.\n\nWhat it is: CVE-2022-0787 is a critical SQL injection vulnerability in Unknown Limit Login Attempts (Spam Protection), published on 28 Mar 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-0787 exists.\n\nAffected product: Unknown Limit Login Attempts (Spam Protection). 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-0787/ (Markdown: https://insights.sbomify.com/CVE-2022-0787/index.md)","id":"CVE-2022-0787","markdown":"https://insights.sbomify.com/CVE-2022-0787/index.md","name":"CVE-2022-0787","record":{"aliases":["GHSA-mv3w-5q88-w6jv"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can perform SQL injection via AJAX actions in the Limit Login Attempts WordPress plugin, potentially accessing or modifying database content.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[{"product":"limit_login_attempts","vendor":"limit_login_attempts_project"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","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 Limit Login Attempts (Spam Protection) WordPress plugin before 5.1 does not sanitise and escape some parameters before using them in SQL statements via AJAX actions (available to unauthenticated users), leading to SQL Injections","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-0787.yaml","stars":null,"title":"Limit Login Attempts (Spam Protection) \u003c 5.1 - SQL Injection"}],"tier":"weaponised"},"has_fix":null,"headline":"Limit Login Attempts (Spam Protection) \u003c 5.1 - Unauthenticated SQLi","id":"CVE-2022-0787","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"WP Fundraising Donation and Crowdfunding Platform \u003c 1.5.0 - Unauthenticated SQLi","id":"CVE-2022-0788"},"packages":[],"prev":{"headline":"KiviCare \u003c 2.3.9 - Unauthenticated SQLi","id":"CVE-2022-0786"},"products":["Limit Login Attempts (Spam Protection)"],"published":"2022-03-28","related":[{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2012-10001","kev_date_added":null,"published":"2021-01-06"},{"cvss_score":7.2,"headline":"Limit Login Attempts \u003c= 1.7.1 - Unauthenticated Stored Cross-Site Scripting","id":"CVE-2023-1912","kev_date_added":null,"published":"2023-04-06"},{"cvss_score":6.1,"headline":"Limit Login Attempts \u003c 4.0.50 - Unauthenticated Stored Cross-Site Scripting","id":"CVE-2021-24657","kev_date_added":null,"published":"2021-09-20"},{"cvss_score":5.4,"headline":"Limit Login Attempts \u003c 1.7.2 - Subscriber+ Stored XSS","id":"CVE-2023-1861","kev_date_added":null,"published":"2023-05-02"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-02","vendors":["Unknown"]},"summary":"Unauthenticated attackers can perform SQL injection via AJAX actions in the Limit Login Attempts WordPress plugin, potentially accessing or modifying database content.","url":"https://insights.sbomify.com/CVE-2022-0787/"}