{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-1702 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-1702 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-1702 is a high-severity SQL injection vulnerability in ultimatemember Ultimate Member – User Profile, Registration, Login, Member Directory, Content Restriction \u0026 Membership Plugin, published on 5 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-1702 and fix it if it is affected.\n\nWhat it is: CVE-2025-1702 is a high-severity SQL injection vulnerability in ultimatemember Ultimate Member – User Profile, Registration, Login, Member Directory, Content Restriction \u0026 Membership Plugin, published on 5 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-1702 in the wild and no public exploit code.\n\nAffected product: ultimatemember Ultimate Member – User Profile, Registration, Login, Member Directory, Content Restriction \u0026 Membership Plugin. 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-1702/ (Markdown: https://insights.sbomify.com/CVE-2025-1702/index.md)","id":"CVE-2025-1702","markdown":"https://insights.sbomify.com/CVE-2025-1702/index.md","name":"CVE-2025-1702","record":{"aliases":["GHSA-5f8v-hjhr-8mx8"],"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 Ultimate Member 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":[],"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 Ultimate Member – User Profile, Registration, Login, Member Directory, Content Restriction \u0026 Membership Plugin plugin for WordPress is vulnerable to time-based SQL Injection via the 'search' parameter in all versions up to, and including, 2.10.0 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":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Ultimate Member \u003c= 2.10.0 - Unauthenticated SQL Injection via search Parameter","id":"CVE-2025-1702","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2025"},"n_packages":0,"n_references":6,"next":{"headline":"Ultimate Blocks \u003c= 3.2.7 - Authenticated (Contributor+) Stored Cross-Site Scripting via content Parameter","id":"CVE-2025-1703"},"packages":[],"prev":{"headline":"Local Privilege Escalation in MIM Admin Service","id":"CVE-2025-1701"},"products":["Ultimate Member – User Profile, Registration, Login, Member Directory, Content Restriction \u0026 Membership Plugin"],"published":"2025-03-05","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["ultimatemember"]},"summary":"Unauthenticated attackers can exploit SQL injection in the Ultimate Member WordPress plugin to extract sensitive database information.","url":"https://insights.sbomify.com/CVE-2025-1702/"}