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 handler loads appointment data based on attacker-supplied appointment IDs without verifying that the appointment's staff_id matches the authenticated staff member's ID. Other related API operations correctly enforce staff scoping, but this method does not, allowing authenticated staff users to enumerate appointment IDs and access appointment details belonging to other staff members. Exposed data includes internal notes and full customer appointment collections with personal and payment information.
Potential Impact
Authenticated staff users with mobile cabinet access can read sensitive appointment and customer data belonging to other staff members. This leads to unauthorized disclosure of personal customer information and payment details. There is no indication of data modification or denial of service impact. The vulnerability has a medium severity rating with a CVSS score of 4.3.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. No official fix or patch information is available at this time. Until a patch is released, restrict staff-level mobile cabinet access to trusted users only and monitor for suspicious activity related to appointment ID enumeration.
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
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 handler loads appointment data based on attacker-supplied appointment IDs without verifying that the appointment's staff_id matches the authenticated staff member's ID. Other related API operations correctly enforce staff scoping, but this method does not, allowing authenticated staff users to enumerate appointment IDs and access appointment details belonging to other staff members. Exposed data includes internal notes and full customer appointment collections with personal and payment information.
Potential Impact
Authenticated staff users with mobile cabinet access can read sensitive appointment and customer data belonging to other staff members. This leads to unauthorized disclosure of personal customer information and payment details. There is no indication of data modification or denial of service impact. The vulnerability has a medium severity rating with a CVSS score of 4.3.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. No official fix or patch information is available at this time. Until a patch is released, restrict staff-level mobile cabinet access to trusted users only and monitor for suspicious activity related to appointment ID enumeration.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Wordfence
- Date Reserved
- 2026-06-22T14:40:37.356Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a813f86bf8831d539784a73
Added to database: 08/16/2026, 04:41:42 UTC
Last enriched: 08/16/2026, 04:57:36 UTC
Last updated: 08/16/2026, 15:30:17 UTC
Views: 5
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.