Overview
A critical security vulnerability, CVE-2025-7038, has been identified in the LatePoint plugin for WordPress, used widely for booking and scheduling appointments. The vulnerability could potentially allow an unauthenticated attacker to bypass authentication and gain unauthorized access to any customer’s account. Given the widespread usage of this plugin across various websites, the impact of this vulnerability could be significant, leading to potential system compromise or data leakage.
Vulnerability Summary
CVE ID: CVE-2025-7038
Severity: High (8.2)
Attack Vector: Network
Privileges Required: None
User Interaction: None
Impact: Unauthorized access to any customer’s account, potential system compromise or data leakage
Affected Products
Escape the Surveillance Era
Most apps won’t tell you the truth.
They’re part of the problem.
Phone numbers. Emails. Profiles. Logs.
It’s all fuel for surveillance.
Ameeba Chat gives you a way out.
- • No phone number
- • No email
- • No personal info
- • Anonymous aliases
- • End-to-end encrypted
Chat without a trace.
Product | Affected Versions
LatePoint Plugin for WordPress | Up to and including 5.1.94
How the Exploit Works
The vulnerability arises due to insufficient identity verification within the `steps__load_step` route of the `latepoint_route_call` AJAX endpoint. The endpoint reads the client-supplied customer email and related customer fields before invoking the internal login handler. It does not verify the login status, capability checks, or a valid AJAX nonce. As a result, an unauthenticated attacker can craft and send a request with any customer’s email and related fields to this endpoint and get logged into the customer’s account.
Conceptual Example Code
A conceptual exploit might look something like this:
POST /wp-admin/admin-ajax.php?action=latepoint_route_call&route_name=steps__load_step HTTP/1.1
Host: target.example.com
Content-Type: application/x-www-form-urlencoded
customer%5Bemail%5D=anyuser%40example.com&customer%5Bphone%5D=1234567890&customer%5Bfirst_name%5D=John&customer%5Blast_name%5D=DoeIn this example, the attacker sends a POST request to the vulnerable endpoint with a customer’s email and related fields. As there is no verification of the login status, capability checks, or a valid AJAX nonce, the server responds by logging into the specified customer’s account.
Mitigation Guidance
Users are strongly advised to apply the latest vendor patches as soon as they become available. In the interim, a Web Application Firewall (WAF) or Intrusion Detection System (IDS) could be used to block or flag attempts to exploit the vulnerability.
