{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-1323 exists.","fix":"No fix has been published for CVE-2025-1323 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-1323 is a high-severity SQL injection vulnerability in wppost WP-Recall – Registration, Profile, Commerce \u0026 More, published on 8 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-1323 and fix it if it is affected.\n\nWhat it is: CVE-2025-1323 is a high-severity SQL injection vulnerability in wppost WP-Recall – Registration, Profile, Commerce \u0026 More, published on 8 Mar 2025. 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-2025-1323 exists.\n\nAffected product: wppost WP-Recall – Registration, Profile, Commerce \u0026 More. 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-2025-1323/ (Markdown: https://insights.sbomify.com/CVE-2025-1323/index.md)","id":"CVE-2025-1323","markdown":"https://insights.sbomify.com/CVE-2025-1323/index.md","name":"CVE-2025-1323","record":{"aliases":["GHSA-93q8-2xpx-g486"],"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 exploit SQL injection in the WP-Recall WordPress plugin to extract sensitive database information.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"wp-recall","vendor":"plechevandrey"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/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 WP-Recall – Registration, Profile, Commerce \u0026 More plugin for WordPress is vulnerable to SQL Injection via the 'databeat' parameter in all versions up to, and including, 16.26.10 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query.  This makes it possible for unauthenticated attackers 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":"2025-05-03","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":1,"refs":[{"date":"2025-05-03T23:06:41Z","kind":"github_poc","ref":"https://github.com/p33d/cve-2025-1323","stars":0,"title":"WP-Recall Plugin SQL Injection "},{"date":null,"kind":"nuclei","ref":"http/cves/2025/CVE-2025-1323.yaml","stars":null,"title":"WP-Recall – Plugin \u003c= 16.26.10 - Unauthenticated SQL Injection"}],"tier":"weaponised"},"has_fix":null,"headline":"WP-Recall – Registration, Profile, Commerce \u0026 More \u003c= 16.26.10 - Unauthenticated SQL Injection","id":"CVE-2025-1323","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Cross-site scripting in WP-Recall – Registration, Profile, Commerce \u0026 More","id":"CVE-2025-1324"},"packages":[],"prev":{"headline":"WP-Recall – Registration, Profile, Commerce \u0026 More \u003c= 16.26.10 - Authenticated (Contributor+) Protected Post Disclosure","id":"CVE-2025-1322"},"products":["WP-Recall – Registration, Profile, Commerce \u0026 More"],"published":"2025-03-08","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":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.7,"headline":"WP-Recall \u003c 16.26.12 - Admin+ SQL Injection","id":"CVE-2024-9770","kev_date_added":null,"published":"2025-03-25"},{"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)"},{"class":"attribution","licence":"MIT","name":"Nuclei templates"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["wppost"]},"summary":"Unauthenticated attackers can exploit SQL injection in the WP-Recall WordPress plugin to extract sensitive database information.","url":"https://insights.sbomify.com/CVE-2025-1323/"}