LatePoint <= 5.1.94 - Unauthenticated Authentication Bypass via load_step Function
Strategic Overview
- Status
- Patched in 5.2.0
- Affected Version
<= 5.1.94- CVSS
- 8.2High
- Weakness type
- CWE-288 · Authentication Bypass Using an Alternate Path or Channel
- CVE
CVE-2025-7038
At a glance
CVE-2025-7038 is a high-severity Authentication Bypass Using an Alternate Path or Channel vulnerability in the Appointment Booking Plugin WordPress plugin, affecting versions <= 5.1.94. It carries a CVSS score of 8.2 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires no authentication. The issue is fixed in version 5.2.0; sites on affected versions should update now. Disclosed September 2025, reported by wesley (wcraft).
Vulnerability Overview
The LatePoint plugin for WordPress is vulnerable to Authentication Bypass due to insufficient identity verification within the steps__load_step route of the latepoint_route_call AJAX endpoint in all versions up to, and including, 5.1.94. The endpoint reads the client-supplied customer email and related customer fields before invoking the internal login handler without verifying login status, capability checks, or a valid AJAX nonce. This makes it possible for unauthenticated attackers to log into any customer’s account.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality.
CWE-288: Authentication Bypass Using an Alternate Path or Channel
Reaching this weakness in Appointment Booking Plugin <= 5.1.94 takes no account at all. Authentication bypass through an alternate path means the application has a second route to a protected action that skips the checks the primary route performs.
The protection on the main path becomes irrelevant, because the attacker simply uses the route that never asks. For Appointment Booking Plugin the fix is 5.2.0: builds <= 5.1.94 are affected, anything from 5.2.0 onward is not.
Remediation
Update to version 5.2.0, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Appointment Booking Plugin 5.2.0 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress
- 9.8CVE-2025-6715: LatePoint <= 5.1.93 Local File Inclusion
CVE-2025-6715 - 9.8CVE-2024-8911: LatePoint <= 5.0.11 Arbitrary User Password Change
CVE-2024-8911 - 9.1CVE-2024-2472: LatePoint Missing Authorization and Info Exposure
CVE-2024-2472 - 8.8CVE-2026-13228: LatePoint Privilege Escalation to Administrator
CVE-2026-13228 - 8.8CVE-2026-49083: LatePoint Privilege Escalation
CVE-2026-49083 - 8.8CVE-2026-6741: LatePoint Privilege Escalation to Administrator
CVE-2026-6741 - 8.8CVE-2026-1566: LatePoint <= 5.2.7 Privilege Escalation
CVE-2026-1566 - 8.8CVE-2025-7052: LatePoint <= 5.1.94 CSRF to Account Takeover
CVE-2025-7052
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C