{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-4302 exists.","fix":"No fix has been published for CVE-2025-4302 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-4302 is a medium-severity vulnerability in Unknown Stop User Enumeration, published on 17 Jul 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-4302 and fix it if it is affected.\n\nWhat it is: CVE-2025-4302 is a medium-severity vulnerability in Unknown Stop User Enumeration, published on 17 Jul 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-4302 exists.\n\nAffected product: Unknown Stop User Enumeration. 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-4302/ (Markdown: https://insights.sbomify.com/CVE-2025-4302/index.md)","id":"CVE-2025-4302","markdown":"https://insights.sbomify.com/CVE-2025-4302/index.md","name":"CVE-2025-4302","record":{"aliases":["GHSA-498r-64c2-wwrm"],"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":"Attackers can bypass user enumeration protection in the Stop User Enumeration plugin by URL-encoding the API path, exposing user data.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[{"product":"stop_user_enumeration","vendor":"fullworksplugins"}],"cvss":{"score":5.3,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[],"description":"The Stop User Enumeration WordPress plugin before version 1.7.3 blocks REST API /wp-json/wp/v2/users/ requests for non-authorized users. However, this can be bypassed by URL-encoding the API path.","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-4302.yaml","stars":null,"title":"Stop User Enumeration WordPress plugin - Authentication Bypass"}],"tier":"weaponised"},"has_fix":null,"headline":"Stop User Enumeration \u003c 1.7.3 - Protection Bypass","id":"CVE-2025-4302","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"PHPGurukul Human Metapneumovirus Testing Management System add-phlebotomist.php sql injection","id":"CVE-2025-4303"},"packages":[],"prev":{"headline":"itsourcecode Content Management System search-notice.php sql injection","id":"CVE-2025-4301"},"products":["Stop User Enumeration"],"published":"2025-07-17","related":[{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2017-18536","kev_date_added":null,"published":"2019-08-21"},{"cvss_score":5.3,"headline":"Information disclosure in n/a","id":"CVE-2017-1000226","kev_date_added":null,"published":"2017-11-17"}],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"attribution","licence":"MIT","name":"Nuclei templates"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-07-17","vendors":["Unknown"]},"summary":"Attackers can bypass user enumeration protection in the Stop User Enumeration plugin by URL-encoding the API path, exposing user data.","url":"https://insights.sbomify.com/CVE-2025-4302/"}