CVE-2026-12905: CWE-639 Authorization Bypass Through User-Controlled Key in ladela Online Scheduling and Appointment Booking System – Bookly
The Bookly plugin for WordPress is vulnerable to Insecure Direct Object Reference in versions up to, and including, 27.7 via the appointment() method of the Mobile Staff Cabinet API (resource=appointment, action=bookly_mobile_staff_cabinet) in frontend/modules/mobile_staff_cabinet/api/handlers/Handler1_0.php. This is due to the handler loading an Appointment by the attacker-supplied params[id] without verifying that the appointment's staff_id matches the authenticated staff member, whereas sibling operations (deleteAppointment, saveAppointment, appointments list) correctly scope to $this->staff->getId() when $this->role === ROLE_STAFF. This makes it possible for authenticated attackers, with staff-level mobile cabinet access (any valid access_key token bound to a Staff entity), to read appointment details — including the internal note and the full customer_appointments collection (customer full_name, email, phone, notes, custom_fields, extras, payment_total, payment_type, payment_status) — belonging to other staff members by enumerating sequential appointment IDs.
AI Analysis
Technical Summary
CVE-2026-12905 describes an insecure direct object reference vulnerability in the Bookly plugin for WordPress, specifically in the appointment() method of the Mobile Staff Cabinet API handler. The vulnerability arises because the handler loads appointment data based on an attacker-controlled parameter without verifying that the appointment belongs to the authenticated staff member. This allows authenticated staff users with valid access_key tokens to enumerate appointment IDs and access sensitive appointment and customer data belonging to other staff members. Other API operations correctly enforce staff scoping, but this method does not, leading to an authorization bypass.
Potential Impact
An attacker with staff-level authenticated access to the mobile staff cabinet can read sensitive appointment details of other staff members. This includes internal notes and comprehensive customer appointment data such as full names, emails, phone numbers, notes, custom fields, extras, and payment information (total, type, status). There is no indication of data modification or denial of service impact. The confidentiality of customer and appointment data is compromised, but integrity and availability are not affected.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict staff-level access to trusted users only and monitor for suspicious enumeration of appointment IDs. Avoid exposing access_key tokens broadly. Follow vendor updates for a security patch addressing this authorization bypass.
CVE-2026-12905: CWE-639 Authorization Bypass Through User-Controlled Key in ladela Online Scheduling and Appointment Booking System – Bookly
Description
The Bookly plugin for WordPress is vulnerable to Insecure Direct Object Reference in versions up to, and including, 27.7 via the appointment() method of the Mobile Staff Cabinet API (resource=appointment, action=bookly_mobile_staff_cabinet) in frontend/modules/mobile_staff_cabinet/api/handlers/Handler1_0.php. This is due to the handler loading an Appointment by the attacker-supplied params[id] without verifying that the appointment's staff_id matches the authenticated staff member, whereas sibling operations (deleteAppointment, saveAppointment, appointments list) correctly scope to $this->staff->getId() when $this->role === ROLE_STAFF. This makes it possible for authenticated attackers, with staff-level mobile cabinet access (any valid access_key token bound to a Staff entity), to read appointment details — including the internal note and the full customer_appointments collection (customer full_name, email, phone, notes, custom_fields, extras, payment_total, payment_type, payment_status) — belonging to other staff members by enumerating sequential appointment IDs.
CVSS v3.1
Score 4.3medium
Affected software
ladela
Online Scheduling and Appointment Booking System – Bookly
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-12905 describes an insecure direct object reference vulnerability in the Bookly plugin for WordPress, specifically in the appointment() method of the Mobile Staff Cabinet API handler. The vulnerability arises because the handler loads appointment data based on an attacker-controlled parameter without verifying that the appointment belongs to the authenticated staff member. This allows authenticated staff users with valid access_key tokens to enumerate appointment IDs and access sensitive appointment and customer data belonging to other staff members. Other API operations correctly enforce staff scoping, but this method does not, leading to an authorization bypass.
Potential Impact
An attacker with staff-level authenticated access to the mobile staff cabinet can read sensitive appointment details of other staff members. This includes internal notes and comprehensive customer appointment data such as full names, emails, phone numbers, notes, custom fields, extras, and payment information (total, type, status). There is no indication of data modification or denial of service impact. The confidentiality of customer and appointment data is compromised, but integrity and availability are not affected.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict staff-level access to trusted users only and monitor for suspicious enumeration of appointment IDs. Avoid exposing access_key tokens broadly. Follow vendor updates for a security patch addressing this authorization bypass.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Wordfence
- Date Reserved
- 2026-06-22T14:40:37.356Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6a813f86bf8831d539784a73
Added to database: 08/16/2026, 04:41:42 UTC
Last enriched: 08/23/2026, 13:23:29 UTC
Last updated: 10/01/2026, 05:08:50 UTC
Views: 33
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.