{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-5692 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-5692 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-5692 is a medium-severity missing authorization vulnerability in smackcoders Lead Form Data Collection to CRM, published on 2 Jul 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-5692 and fix it if it is affected.\n\nWhat it is: CVE-2025-5692 is a medium-severity missing authorization vulnerability in smackcoders Lead Form Data Collection to CRM, published on 2 Jul 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-5692 in the wild and no public exploit code.\n\nAffected product: smackcoders Lead Form Data Collection to CRM. 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-5692/ (Markdown: https://insights.sbomify.com/CVE-2025-5692/index.md)","id":"CVE-2025-5692","markdown":"https://insights.sbomify.com/CVE-2025-5692/index.md","name":"CVE-2025-5692","record":{"aliases":["GHSA-fqjp-v5r7-6qw9"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Authenticated subscribers can modify plugin settings due to missing capability checks in the Lead Form Data Collection to CRM WordPress plugin.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"lead_form_data_collection_to_crm","vendor":"smackcoders"}],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"The Lead Form Data Collection to CRM plugin for WordPress is vulnerable to unauthorized access due to a missing capability check on several functions in the ~/includes/LB_admin_ajax.php file in all versions up to, and including, 3.1. This makes it possible for authenticated attackers, with Subscriber-level access and above, to perform several actions like updating settings. Initially this CVE was assigned specifically to all AJAX actions and the doFieldAjaxAction() function, however it was determined that CVE-2025-47690 is assigned to the doFieldAjaxAction() function that leads to arbitrary options updates.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Lead Form Data Collection to CRM \u003c= 3.1 - Missing Authorization to Authenticated (Subscriber+) Many Actions","id":"CVE-2025-5692","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"PHPGurukul Human Metapneumovirus Testing Management System bwdates-report-result.php sql injection","id":"CVE-2025-5693"},"packages":[],"prev":{"headline":"Cursor allows PostgreSQL Anonymizer masked user to gain unauthorized access to authentic data","id":"CVE-2025-5690"},"products":["Lead Form Data Collection to CRM"],"published":"2025-07-02","related":[],"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":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["smackcoders"]},"summary":"Authenticated subscribers can modify plugin settings due to missing capability checks in the Lead Form Data Collection to CRM WordPress plugin.","url":"https://insights.sbomify.com/CVE-2025-5692/"}