CVE-2025-5692 Vulnerability Analysis & Exploit Details

CVE-2025-5692
Vulnerability Scoring

6.3
/10
High Risk

If left unpatched, CVE-2025-5692 could lead to major system disruptions or data loss.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: Low
    Some privileges are necessary to exploit the vulnerability.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2025-5692 Details

Status: Modified

Last updated: 🕑 27 Aug 2025, 14:15 UTC
Originally published on: 🕒 02 Jul 2025, 03:15 UTC

Time between publication and last update: 56 days

CVSS Release: version 3

CVSS3 Source

security@wordfence.com

CVSS3 Type

Primary

CVSS3 Vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

CVE-2025-5692 Vulnerability Summary

CVE-2025-5692: 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.

Assessing the Risk of CVE-2025-5692

Access Complexity Graph

The exploitability of CVE-2025-5692 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2025-5692

CVE-2025-5692 presents an accessible attack vector with minimal effort required. Restricting access controls and implementing security updates are critical to reducing exploitation risks.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2025-5692, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2025-5692, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: Low
    CVE-2025-5692 could lead to minor leaks of non-critical information without major privacy breaches.
  • Integrity: Low
    Exploiting CVE-2025-5692 may cause minor changes to data without severely impacting its accuracy.
  • Availability: Low
    CVE-2025-5692 may slightly degrade system performance without fully affecting service availability.

CVE-2025-5692 References

External References

CWE Common Weakness Enumeration

CWE-862

CAPEC Common Attack Pattern Enumeration and Classification

  • Exploitation of Thunderbolt Protection Flaws CAPEC-665 An adversary leverages a firmware weakness within the Thunderbolt protocol, on a computing device to manipulate Thunderbolt controller firmware in order to exploit vulnerabilities in the implementation of authorization and verification schemes within Thunderbolt protection mechanisms. Upon gaining physical access to a target device, the adversary conducts high-level firmware manipulation of the victim Thunderbolt controller SPI (Serial Peripheral Interface) flash, through the use of a SPI Programing device and an external Thunderbolt device, typically as the target device is booting up. If successful, this allows the adversary to modify memory, subvert authentication mechanisms, spoof identities and content, and extract data and memory from the target device. Currently 7 major vulnerabilities exist within Thunderbolt protocol with 9 attack vectors as noted in the Execution Flow.

Vulnerable Configurations

  • cpe:2.3:a:smackcoders:lead_form_data_collection_to_crm:1.2:*:*:*:*:wordpress:*:*
    cpe:2.3:a:smackcoders:lead_form_data_collection_to_crm:1.2:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:smackcoders:lead_form_data_collection_to_crm:1.2.1:*:*:*:*:wordpress:*:*
    cpe:2.3:a:smackcoders:lead_form_data_collection_to_crm:1.2.1:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:smackcoders:lead_form_data_collection_to_crm:1.3:*:*:*:*:wordpress:*:*
    cpe:2.3:a:smackcoders:lead_form_data_collection_to_crm:1.3:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:smackcoders:lead_form_data_collection_to_crm:1.3.1:*:*:*:*:wordpress:*:*
    cpe:2.3:a:smackcoders:lead_form_data_collection_to_crm:1.3.1:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:smackcoders:lead_form_data_collection_to_crm:1.3.2:*:*:*:*:wordpress:*:*
    cpe:2.3:a:smackcoders:lead_form_data_collection_to_crm:1.3.2:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:smackcoders:lead_form_data_collection_to_crm:1.4:*:*:*:*:wordpress:*:*
    cpe:2.3:a:smackcoders:lead_form_data_collection_to_crm:1.4:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:smackcoders:lead_form_data_collection_to_crm:1.4.1:*:*:*:*:wordpress:*:*
    cpe:2.3:a:smackcoders:lead_form_data_collection_to_crm:1.4.1:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:smackcoders:lead_form_data_collection_to_crm:1.5:*:*:*:*:wordpress:*:*
    cpe:2.3:a:smackcoders:lead_form_data_collection_to_crm:1.5:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:smackcoders:lead_form_data_collection_to_crm:1.5.1:*:*:*:*:wordpress:*:*
    cpe:2.3:a:smackcoders:lead_form_data_collection_to_crm:1.5.1:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:smackcoders:lead_form_data_collection_to_crm:1.5.2:*:*:*:*:wordpress:*:*
    cpe:2.3:a:smackcoders:lead_form_data_collection_to_crm:1.5.2:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:smackcoders:lead_form_data_collection_to_crm:1.5.3:*:*:*:*:wordpress:*:*
    cpe:2.3:a:smackcoders:lead_form_data_collection_to_crm:1.5.3:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:smackcoders:lead_form_data_collection_to_crm:1.9:*:*:*:*:wordpress:*:*
    cpe:2.3:a:smackcoders:lead_form_data_collection_to_crm:1.9:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:smackcoders:lead_form_data_collection_to_crm:2.0:*:*:*:*:wordpress:*:*
    cpe:2.3:a:smackcoders:lead_form_data_collection_to_crm:2.0:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:smackcoders:lead_form_data_collection_to_crm:2.1:*:*:*:*:wordpress:*:*
    cpe:2.3:a:smackcoders:lead_form_data_collection_to_crm:2.1:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:smackcoders:lead_form_data_collection_to_crm:2.1.1:*:*:*:*:wordpress:*:*
    cpe:2.3:a:smackcoders:lead_form_data_collection_to_crm:2.1.1:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:smackcoders:lead_form_data_collection_to_crm:2.1.2:*:*:*:*:wordpress:*:*
    cpe:2.3:a:smackcoders:lead_form_data_collection_to_crm:2.1.2:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:smackcoders:lead_form_data_collection_to_crm:2.1.3:*:*:*:*:wordpress:*:*
    cpe:2.3:a:smackcoders:lead_form_data_collection_to_crm:2.1.3:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:smackcoders:lead_form_data_collection_to_crm:2.1.4:*:*:*:*:wordpress:*:*
    cpe:2.3:a:smackcoders:lead_form_data_collection_to_crm:2.1.4:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:smackcoders:lead_form_data_collection_to_crm:2.1.5:*:*:*:*:wordpress:*:*
    cpe:2.3:a:smackcoders:lead_form_data_collection_to_crm:2.1.5:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:smackcoders:lead_form_data_collection_to_crm:2.2:*:*:*:*:wordpress:*:*
    cpe:2.3:a:smackcoders:lead_form_data_collection_to_crm:2.2:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:smackcoders:lead_form_data_collection_to_crm:2.3:*:*:*:*:wordpress:*:*
    cpe:2.3:a:smackcoders:lead_form_data_collection_to_crm:2.3:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:smackcoders:lead_form_data_collection_to_crm:2.3.1:*:*:*:*:wordpress:*:*
    cpe:2.3:a:smackcoders:lead_form_data_collection_to_crm:2.3.1:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:smackcoders:lead_form_data_collection_to_crm:2.3.2:*:*:*:*:wordpress:*:*
    cpe:2.3:a:smackcoders:lead_form_data_collection_to_crm:2.3.2:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:smackcoders:lead_form_data_collection_to_crm:2.3.3:*:*:*:*:wordpress:*:*
    cpe:2.3:a:smackcoders:lead_form_data_collection_to_crm:2.3.3:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:smackcoders:lead_form_data_collection_to_crm:2.3.4:*:*:*:*:wordpress:*:*
    cpe:2.3:a:smackcoders:lead_form_data_collection_to_crm:2.3.4:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:smackcoders:lead_form_data_collection_to_crm:2.3.5:*:*:*:*:wordpress:*:*
    cpe:2.3:a:smackcoders:lead_form_data_collection_to_crm:2.3.5:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:smackcoders:lead_form_data_collection_to_crm:2.3.6:*:*:*:*:wordpress:*:*
    cpe:2.3:a:smackcoders:lead_form_data_collection_to_crm:2.3.6:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:smackcoders:lead_form_data_collection_to_crm:2.3.7:*:*:*:*:wordpress:*:*
    cpe:2.3:a:smackcoders:lead_form_data_collection_to_crm:2.3.7:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:smackcoders:lead_form_data_collection_to_crm:2.3.8:*:*:*:*:wordpress:*:*
    cpe:2.3:a:smackcoders:lead_form_data_collection_to_crm:2.3.8:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:smackcoders:lead_form_data_collection_to_crm:2.3.9:*:*:*:*:wordpress:*:*
    cpe:2.3:a:smackcoders:lead_form_data_collection_to_crm:2.3.9:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:smackcoders:lead_form_data_collection_to_crm:2.4:*:*:*:*:wordpress:*:*
    cpe:2.3:a:smackcoders:lead_form_data_collection_to_crm:2.4:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:smackcoders:lead_form_data_collection_to_crm:2.5:*:*:*:*:wordpress:*:*
    cpe:2.3:a:smackcoders:lead_form_data_collection_to_crm:2.5:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:smackcoders:lead_form_data_collection_to_crm:2.5.1:*:*:*:*:wordpress:*:*
    cpe:2.3:a:smackcoders:lead_form_data_collection_to_crm:2.5.1:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:smackcoders:lead_form_data_collection_to_crm:2.5.2:*:*:*:*:wordpress:*:*
    cpe:2.3:a:smackcoders:lead_form_data_collection_to_crm:2.5.2:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:smackcoders:lead_form_data_collection_to_crm:2.5.3:*:*:*:*:wordpress:*:*
    cpe:2.3:a:smackcoders:lead_form_data_collection_to_crm:2.5.3:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:smackcoders:lead_form_data_collection_to_crm:2.6:*:*:*:*:wordpress:*:*
    cpe:2.3:a:smackcoders:lead_form_data_collection_to_crm:2.6:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:smackcoders:lead_form_data_collection_to_crm:3.0:*:*:*:*:wordpress:*:*
    cpe:2.3:a:smackcoders:lead_form_data_collection_to_crm:3.0:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:smackcoders:lead_form_data_collection_to_crm:3.0.1:*:*:*:*:wordpress:*:*
    cpe:2.3:a:smackcoders:lead_form_data_collection_to_crm:3.0.1:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:smackcoders:lead_form_data_collection_to_crm:3.1:*:*:*:*:wordpress:*:*
    cpe:2.3:a:smackcoders:lead_form_data_collection_to_crm:3.1:*:*:*:*:wordpress:*:*

Protect Your Infrastructure against CVE-2025-5692: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2025-10127 – Daikin Security Gateway is vulnerable to an authorization bypass through a user-controlled key vulnerability that could allow an attacker to bypa...
  • CVE-2025-9319 – A potential vulnerability was reported in the Lenovo Wallpaper Client that could allow arbitrary code execution under certain conditions.
  • CVE-2025-9214 – A missing authentication vulnerability was reported in some Lenovo printers that could allow a user to view limited device information or modify ne...
  • CVE-2025-9201 – A potential DLL hijacking vulnerability was discovered in Lenovo Browser during an internal security assessment that could allow a local user to ex...
  • CVE-2025-8557 – An internal product security audit of Lenovo XClarity Orchestrator (LXCO) discovered the below vulnerability: An attacker with access to a device ...