Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-5692: CWE-862 Missing Authorization in smackcoders Lead Form Data Collection to CRM

0
Medium
VulnerabilityCVE-2025-5692cvecve-2025-5692cwe-862
Published: Wed Jul 02 2025 (07/02/2025, 02:03:53 UTC)
Source: CVE Database V5
Vendor/Project: smackcoders
Product: Lead Form Data Collection to CRM

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.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 02/27/2026, 15:29:47 UTC

Technical Analysis

CVE-2025-5692 identifies a missing authorization vulnerability (CWE-862) in the 'Lead Form Data Collection to CRM' WordPress plugin developed by smackcoders. The issue exists in all versions up to and including 3.1, specifically within the ~/includes/LB_admin_ajax.php file where several AJAX functions lack proper capability checks. This omission allows any authenticated user with Subscriber-level access or above to invoke these AJAX endpoints and perform unauthorized actions, such as modifying plugin settings. The vulnerability is exploitable remotely without user interaction and requires only low privileges, which are commonly granted to registered users on WordPress sites. The CVSS 3.1 base score is 6.3 (medium severity), reflecting network attack vector, low attack complexity, and partial impact on confidentiality, integrity, and availability. This vulnerability is separate from CVE-2025-47690, which concerns arbitrary option updates via the doFieldAjaxAction() function. No patches have been linked yet, and no known exploits are reported in the wild. The flaw could be leveraged for privilege escalation or to disrupt CRM data collection processes by altering plugin configurations.

Potential Impact

The vulnerability allows authenticated users with minimal privileges (Subscriber-level) to perform unauthorized actions within the plugin, potentially leading to unauthorized changes in CRM data collection settings. This can result in data integrity issues, unauthorized data exposure, or denial of service if settings are manipulated to disrupt normal operations. Organizations relying on this plugin for lead data collection risk compromised data accuracy and potential leakage of sensitive customer information. Attackers could also use this flaw as a stepping stone for further privilege escalation or lateral movement within the WordPress environment. Although the impact is limited to sites using this specific plugin, the widespread use of WordPress and CRM integrations means many organizations worldwide could be affected. The absence of known exploits reduces immediate risk, but the ease of exploitation and low privilege requirement make it a significant concern.

Mitigation Recommendations

Organizations should immediately audit their WordPress installations for the presence of the 'Lead Form Data Collection to CRM' plugin and verify the version in use. Until an official patch is released, administrators should restrict plugin access strictly to trusted users and consider temporarily disabling the plugin if feasible. Implementing Web Application Firewall (WAF) rules to block unauthorized AJAX requests targeting LB_admin_ajax.php endpoints can reduce exposure. Monitoring logs for suspicious AJAX activity from low-privilege accounts is recommended. Additionally, site administrators should review user roles and permissions to ensure minimal privilege assignment, limiting Subscriber-level users' capabilities where possible. Once a patch is available, prompt updating to the fixed version is critical. Employing security plugins that enforce capability checks or custom code to add authorization validation to the vulnerable functions can serve as interim controls.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.1
Assigner Short Name
Wordfence
Date Reserved
2025-06-04T20:04:29.128Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 68649be16f40f0eb729133b2

Added to database: 7/2/2025, 2:39:29 AM

Last enriched: 2/27/2026, 3:29:47 PM

Last updated: 3/25/2026, 12:15:11 AM

Views: 137

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses