---
id: "CVE-2026-110653"
kind: "vulnerability"
aliases: ["CVE-2026-110653"]
title: "The Appointment Booking Plugin \u2013 LatePoint | Calendar & Scheduling for WordPress plugin for WordPress is vulnerable\u2026"
severity: "critical"
cvss: 9.1
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["customer-accounts", "latepoint", "package", "wordpress"]
not_affected_if: ["plugin-not-installed", "version-above-5.7.4"]
published_at: "2026-10-17T03:16:28+00:00"
first_seen_at: "2026-10-23T21:57:14+00:00"
updated_at: "2026-10-23T22:28:55+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-110653", "first_seen_at": "2026-10-23T21:57:14+00:00"}]
---

# The Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress plugin for WordPress is vulnerable…

LatePoint, a WordPress appointment booking plugin, has a race condition in its OTP login check that lets concurrent requests bypass the 10-attempt lockout. An unauthenticated attacker who knows a customer's email or phone can brute-force the 6-digit code and log in as that customer, reaching their account, bookings and personal data.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

Check the installed LatePoint version in the WordPress plugins screen or the plugin header; unknown whether a file or setting check is available.

## Fix

Update LatePoint to a release newer than 5.7.4; the patched version is unknown from the sources.

## Timeline

- 2026-10-23T21:57:14+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-110653

## From the sources

The Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress plugin for WordPress is vulnerable to Authentication Bypass via Race Condition in all versions up to, and including, 5.7.4. This is due to a non-atomic read-modify-write on the OTP verification attempts counter in the `verifyOTP` function: the counter is incremented using a stale in-memory value with no conditional `WHERE attempts < 10` guard on the `UPDATE` and no `SELECT ... FOR UPDATE` row lock, creating a TOCTOU window that allows concurrent requests to bypass the 10-attempt lockout. This makes it possible for unauthenticated attackers — who know a target customer's registered email address or phone number — to fire concurrent requests to the `auth__verify_otp` endpoint, defeat the lockout cap, brute-force the 6-digit OTP code, and authenticate as the targeted LatePoint customer, gaining full access to their account, bookings, and personal data. The nonce check present on the endpoint (`otp_verify_otp_nonce`) does not mitigate this issue, as the nonce is publicly emitted by the unauthenticated `request_otp` and `resend_otp` endpoints and is trivially obtainable by any unauthenticated attacker prior to launching the race.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_