# CVE-2026-110653: LatePoint WordPress plugin authentication bypass via race condition

Source: https://junglewise.ai/threats/cve-2026-110653-the-appointment-booking-plugin-latepoint-calendar-scheduling-for  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-17. Updated: 2026-10-17  
License: CC BY 4.0 with a link back

CVE-2026-110653 · Severity: critical · CVSS 9.1 · Published 2026-10-17

LatePoint is a WordPress booking and scheduling plugin that allows customers to book appointments. An attacker who knows a customer's email or phone number can exploit a race condition in the OTP verification system to bypass the login attempt lockout, brute-force the 6-digit OTP code, and gain full access to the customer's account, bookings, and personal data.

Technologies: [LatePoint](https://junglewise.ai/threats/technologies/latepoint). Vendors: [LatePoint](https://junglewise.ai/threats/vendors/latepoint).

## Quick answers

**Is CVE-2026-110653 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-110653 being exploited in the wild.

**How severe is CVE-2026-110653?** Critical severity, with a CVSS score of 9.1, published 17 October 2026.

**Which products and versions are affected?** LatePoint up to and including 5.7.4.

**Is there a fix for CVE-2026-110653?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-110653 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-110653?** Check whether you run LatePoint at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

The vulnerability is a TOCTOU race condition in the verifyOTP function where the OTP attempt counter is incremented using a stale in-memory value without atomic transactions or row-level locking. An unauthenticated attacker can fire concurrent requests to the auth__verify_otp endpoint to bypass the 10-attempt lockout, brute-force the OTP code, and authenticate as any customer whose email or phone is known. The publicly obtainable nonce from unauthenticated endpoints does not provide protection.

## Affected products

- LatePoint LatePoint up to and including 5.7.4

## Timeline

- 2026-10-17: disclosed

## References

- [https://plugins.trac.wordpress.org/browser/latepoint/tags/5.7.4/lib/controllers/auth_controller.php](https://plugins.trac.wordpress.org/browser/latepoint/tags/5.7.4/lib/controllers/auth_controller.php)
- [https://plugins.trac.wordpress.org/browser/latepoint/tags/5.7.4/lib/controllers/auth_controller.php](https://plugins.trac.wordpress.org/browser/latepoint/tags/5.7.4/lib/controllers/auth_controller.php)

## Related threats

- [LatePoint authentication bypass via SQL injection in password reset](https://junglewise.ai/threats/cve-2026-118066-the-appointment-booking-plugin-latepoint-calendar-scheduling-for)
- [LatePoint stored cross-site scripting in customer email parameter](https://junglewise.ai/threats/cve-2026-119152-the-appointment-booking-plugin-latepoint-calendar-scheduling-for)
- [LatePoint WordPress plugin stored XSS in booking form settings](https://junglewise.ai/threats/cve-2026-105258-the-appointment-booking-plugin-wordpress-plugin-before-5-7-6)
- [LatePoint WordPress plugin payment bypass in booking checkout](https://junglewise.ai/threats/cve-2026-105256-the-latepoint-wordpress-plugin-before-5-7-5-does-not-validate)
- [LatePoint WordPress plugin IDOR in customer data access](https://junglewise.ai/threats/cve-2026-105257-the-appointment-booking-plugin-wordpress-plugin-before-5-7-5)