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-7052: CWE-352 Cross-Site Request Forgery (CSRF) in latepoint LatePoint – Calendar Booking Plugin for Appointments and Events

0
High
VulnerabilityCVE-2025-7052cvecve-2025-7052cwe-352
Published: Tue Sep 30 2025 (09/30/2025, 04:27:07 UTC)
Source: CVE Database V5
Vendor/Project: latepoint
Product: LatePoint – Calendar Booking Plugin for Appointments and Events

Description

CVE-2025-7052 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability affecting all versions up to 5. 1. 94 of the LatePoint WordPress plugin. The flaw arises from missing nonce validation on the change_password() function accessed via an AJAX route, allowing unauthenticated attackers to trick logged-in users into changing their passwords via malicious links. This vulnerability can lead to full account takeover, impacting confidentiality, integrity, and availability of user accounts. Exploitation requires user interaction but no authentication, making it relatively easy to exploit. There are no known exploits in the wild yet, but the high CVSS score (8. 8) indicates significant risk. European organizations using LatePoint for appointment bookings should prioritize patching or mitigating this issue. Countries with high WordPress adoption and significant small-to-medium business sectors relying on appointment plugins are most at risk.

AI-Powered Analysis

AILast updated: 10/07/2025, 11:33:05 UTC

Technical Analysis

The LatePoint plugin for WordPress, widely used for calendar booking and appointment management, suffers from a critical CSRF vulnerability identified as CVE-2025-7052. This vulnerability exists in all versions up to and including 5.1.94 due to the absence of nonce validation in the change_password() function, which is exposed via the AJAX route customer_cabinet__change_password. The plugin registers this endpoint with both wp_ajax and wp_ajax_nopriv hooks but fails to verify user capabilities or nonce tokens before allowing password resets. Consequently, an unauthenticated attacker can craft a malicious link that, when visited by a logged-in customer or administrator (if “WP users as customers” is enabled), triggers a password change without the victim's consent. This attack vector leverages the CWE-352 CSRF weakness, enabling attackers to hijack accounts by exploiting the victim's active session. The vulnerability impacts confidentiality (account takeover), integrity (unauthorized password changes), and availability (potential account lockout). The CVSS 3.1 score of 8.8 reflects the vulnerability's network attack vector, low attack complexity, no privileges required, user interaction needed, and high impact on confidentiality, integrity, and availability. Although no public exploits are currently known, the ease of exploitation and severity necessitate urgent attention from affected users and administrators.

Potential Impact

For European organizations, the impact of CVE-2025-7052 is significant, especially for businesses relying on the LatePoint plugin for customer appointment scheduling and management. Successful exploitation can lead to unauthorized account takeovers, enabling attackers to manipulate booking data, access sensitive customer information, or disrupt service availability. This can result in reputational damage, regulatory non-compliance (e.g., GDPR violations due to unauthorized data access), financial losses from service disruption or fraud, and increased operational costs for incident response and remediation. Small and medium enterprises (SMEs) using WordPress with LatePoint are particularly vulnerable, as they may lack dedicated security teams to detect or mitigate such attacks promptly. The vulnerability also poses risks to administrators if the “WP users as customers” feature is enabled, potentially compromising higher privilege accounts and leading to broader system compromise. Given the widespread use of WordPress in Europe and the popularity of appointment booking plugins, the threat landscape is broad, affecting sectors such as healthcare, legal services, education, and retail that rely on online scheduling.

Mitigation Recommendations

To mitigate CVE-2025-7052 effectively, organizations should: 1) Immediately update the LatePoint plugin to a patched version once released by the vendor; 2) If a patch is not yet available, temporarily disable or restrict access to the vulnerable AJAX endpoint (customer_cabinet__change_password) via web application firewall (WAF) rules or server configuration; 3) Implement custom nonce validation and user capability checks on the change_password() function to prevent unauthorized requests; 4) Enforce multi-factor authentication (MFA) for WordPress user accounts to reduce the impact of compromised credentials; 5) Educate users about phishing and social engineering risks to minimize the likelihood of clicking malicious links; 6) Monitor logs for suspicious password change requests and anomalous user activity; 7) Review and limit the use of the “WP users as customers” feature if not essential, to reduce attack surface; 8) Employ security plugins that detect and block CSRF attempts and unauthorized AJAX calls; 9) Conduct regular security audits and penetration tests focusing on plugin vulnerabilities; 10) Maintain up-to-date backups to enable recovery in case of compromise.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
Wordfence
Date Reserved
2025-07-03T19:21:30.973Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 68db5dce3dea812c77a6ce67

Added to database: 9/30/2025, 4:34:22 AM

Last enriched: 10/7/2025, 11:33:05 AM

Last updated: 11/14/2025, 4:30:44 AM

Views: 88

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 enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats