{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-2221 exists.","fix":"No fix has been published for CVE-2025-2221 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-2221 is a high-severity SQL injection vulnerability in whyun WPCOM Member, published on 14 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-2221 and fix it if it is affected.\n\nWhat it is: CVE-2025-2221 is a high-severity SQL injection vulnerability in whyun WPCOM Member, published on 14 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-2221 exists.\n\nAffected product: whyun WPCOM Member. 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-2221/ (Markdown: https://insights.sbomify.com/CVE-2025-2221/index.md)","id":"CVE-2025-2221","markdown":"https://insights.sbomify.com/CVE-2025-2221/index.md","name":"CVE-2025-2221","record":{"aliases":["GHSA-938x-rjx9-c9f3"],"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 time-based SQL injection to extract sensitive database information from the WPCOM Member plugin.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"wpcom_member","vendor":"wpcom"}],"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 WPCOM Member plugin for WordPress is vulnerable to time-based SQL Injection via the ‘user_phone’ parameter in all versions up to, and including, 1.7.6 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":1,"refs":[{"date":null,"kind":"nuclei","ref":"http/cves/2025/CVE-2025-2221.yaml","stars":null,"title":"WordPress WPCOM Member \u003c= 1.7.6 - SQL Injection"}],"tier":"weaponised"},"has_fix":null,"headline":"WPCOM Member \u003c= 1.7.6 - Unauthenticated Time-Based SQL Injection","id":"CVE-2025-2221","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"Information disclosure in ConneXium Network Manager","id":"CVE-2025-2222"},"packages":[],"prev":{"headline":"Odyssey CMS reCAPTCHA odyssey_contact_form.php key management","id":"CVE-2025-2220"},"products":["WPCOM Member"],"published":"2025-03-14","related":[{"cvss_score":9.8,"headline":"WPCOM Member \u003c= 1.5.2.1 - Unauthenticated Privilege Escalation via User Meta","id":"CVE-2024-7493","kev_date_added":null,"published":"2024-09-06"},{"cvss_score":7.1,"headline":"WordPress WPCOM Member plugin \u003c= 1.5.4 - Reflected Cross Site Scripting (XSS) vulnerability","id":"CVE-2024-47378","kev_date_added":null,"published":"2024-10-05"}],"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":"partial"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["whyun"]},"summary":"Unauthenticated attackers can exploit time-based SQL injection to extract sensitive database information from the WPCOM Member plugin.","url":"https://insights.sbomify.com/CVE-2025-2221/"}