{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-9770 exists.","fix":"No fix has been published for CVE-2024-9770 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-9770 is a medium-severity SQL injection vulnerability in Unknown WP-Recall, published on 25 Mar 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2024-9770 and fix it if it is affected.\n\nWhat it is: CVE-2024-9770 is a medium-severity SQL injection vulnerability in Unknown WP-Recall, published on 25 Mar 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-9770 exists.\n\nAffected product: Unknown WP-Recall. 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-2024-9770/ (Markdown: https://insights.sbomify.com/CVE-2024-9770/index.md)","id":"CVE-2024-9770","markdown":"https://insights.sbomify.com/CVE-2024-9770/index.md","name":"CVE-2024-9770","record":{"aliases":["GHSA-5wqh-pcq3-r3px"],"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":"Administrators can execute SQL injection attacks in the WP-Recall WordPress plugin due to unsanitized parameters in SQL statements.","user_interaction":"required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[{"product":"wp-recall","vendor":"plechevandrey"}],"cvss":{"score":4.7,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"The WP-Recall  WordPress plugin before 16.26.12 does not sanitize and escape a parameter before using it in a SQL statement, allowing admins to perform SQL injection attacks","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"WP-Recall \u003c 16.26.12 - Admin+ SQL Injection","id":"CVE-2024-9770","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"WP-Recall \u003c 16.26.12 - Admin+ Stored XSS","id":"CVE-2024-9771"},"packages":[],"prev":{"headline":"Video Gallery \u003c= 2.4.1 - Authenticated (Administrator+) Stored Cross-Site Scripting","id":"CVE-2024-9769"},"products":["WP-Recall"],"published":"2025-03-25","related":[{"cvss_score":9.8,"headline":"Auth bypass in WP-Recall – Registration, Profile, Commerce \u0026 More","id":"CVE-2024-8292","kev_date_added":null,"published":"2024-09-06"},{"cvss_score":7.5,"headline":"WP-Recall – Registration, Profile, Commerce \u0026 More \u003c= 16.26.10 - Unauthenticated SQL Injection","id":"CVE-2025-1323","kev_date_added":null,"published":"2025-03-08"},{"cvss_score":6.4,"headline":"Cross-site scripting in WP-Recall – Registration, Profile, Commerce \u0026 More","id":"CVE-2025-1324","kev_date_added":null,"published":"2025-03-08"},{"cvss_score":6.3,"headline":"Missing authorization in WP-Recall – Registration, Profile, Commerce \u0026 More","id":"CVE-2025-1325","kev_date_added":null,"published":"2025-03-08"},{"cvss_score":5.3,"headline":"WP-Recall – Registration, Profile, Commerce \u0026 More \u003c= 16.26.6 - Unauthenticated Payment Deletion via delete_payment","id":"CVE-2024-1175","kev_date_added":null,"published":"2024-06-06"},{"cvss_score":4.3,"headline":"WP-Recall – Registration, Profile, Commerce \u0026 More \u003c= 16.26.10 - Authenticated (Contributor+) Protected Post Disclosure","id":"CVE-2025-1322","kev_date_added":null,"published":"2025-03-08"}],"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":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-03-25","vendors":["Unknown"]},"summary":"Administrators can execute SQL injection attacks in the WP-Recall WordPress plugin due to unsanitized parameters in SQL statements.","url":"https://insights.sbomify.com/CVE-2024-9770/"}