LatePoint – Calendar Booking Plugin for Appointments and Events <= 5.2.6 - Authenticated (Subscriber+) Insecure Direct Object Reference
Strategic Overview
- Status
- Patched in 5.2.7
- Affected Version
<= 5.2.6- CVSS
- 4.3Medium
- Weakness type
- CWE-639 · Authorization Bypass Through User-Controlled Key
- CVE
CVE-2026-32533
At a glance
CVE-2026-32533 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Appointment Booking Plugin WordPress plugin, affecting versions <= 5.2.6. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 5.2.7; sites on affected versions should update now. Disclosed March 2026, reported by daroo.
Vulnerability Overview
The LatePoint – Calendar Booking Plugin for Appointments and Events plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 5.2.6 due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with Subscriber-level access and above, to perform unauthorized actions.
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 interaction from a victim user.
CWE-639: Authorization Bypass Through User-Controlled Key
Reaching this weakness in Appointment Booking Plugin <= 5.2.6 takes an account at Subscriber level or above. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.
Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For Appointment Booking Plugin the fix is 5.2.7: builds <= 5.2.6 are affected, anything from 5.2.7 onward is not.
Remediation
Update to version 5.2.7, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Appointment Booking Plugin 5.2.7 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-8943: LatePoint <= 5.0.12 Authentication Bypass
CVE-2024-8943 - 9.8CVE-2024-8911: LatePoint <= 5.0.11 Arbitrary User Password Change
CVE-2024-8911 - 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