LatePoint <= 5.6.2 - Unauthenticated Insecure Direct Object Reference to Arbitrary Creation via 'service_id' Parameter
Strategic Overview
- Status
- Patched in 5.6.3
- Affected Version
<= 5.6.2- CVSS
- 5.3Medium
- Weakness type
- CWE-639 · Authorization Bypass Through User-Controlled Key
- CVE
CVE-2026-12657
At a glance
CVE-2026-12657 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Appointment Booking Plugin WordPress plugin, affecting versions <= 5.6.2. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 5.6.3; sites on affected versions should update now. Disclosed July 2026, reported by gidget smith.
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.6.2 via the 'service_id' parameter due to missing validation on a user controlled key. This makes it possible for unauthenticated attackers to create approved bookings against services explicitly restricted to admins and agents, consuming restricted appointment capacity and triggering unauthorized bookings for admin/agent-only services. The bypass works via both the params[booking][service_id] parameter in steps__load_step and the presets[selected_service] parameter in steps__start, both of which are publicly accessible without authentication.
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.
CWE-639: Authorization Bypass Through User-Controlled Key
Appointment Booking Plugin <= 5.6.2 carries this weakness at service_id, and reaching it takes no account at all. 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.6.3: builds <= 5.6.2 are affected, anything from 5.6.3 onward is not.
Remediation
Update to version 5.6.3, 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.6.3 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