Ladela Bookly Plugin up to 27.7 on WordPress Mobile Staff Cabinet API Handler1_0.php appointment ID resource injection

Summaryinfo

A vulnerability marked as problematic has been reported in Ladela Bookly Plugin up to 27.7. Affected by this issue is the function appointment of the file frontend/modules/mobile_staff_cabinet/api/handlers/Handler1_0.php of the component Mobile Staff Cabinet API. The manipulation of the argument ID leads to resource injection. This vulnerability is listed as CVE-2026-12905. The attack may be initiated remotely. There is no available exploit.

Detailsinfo

A vulnerability was found in Ladela Bookly Plugin up to 27.7 and classified as problematic. This issue affects the function appointment of the file frontend/modules/mobile_staff_cabinet/api/handlers/Handler1_0.php of the component Mobile Staff Cabinet API. The manipulation of the argument id with an unknown input leads to a resource injection vulnerability. Using CWE to declare the problem leads to CWE-99. The product receives input from an upstream component, but it does not restrict or incorrectly restricts the input before it is used as an identifier for a resource that may be outside the intended sphere of control. Impacted is confidentiality. The summary by CVE is:

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.

The advisory is shared at wordfence.com. The identification of this vulnerability is CVE-2026-12905 since 06/22/2026. The exploitation is known to be easy. The attack may be initiated remotely. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 08/16/2026).

By approaching the search of inurl:frontend/modules/mobile_staff_cabinet/api/handlers/Handler1_0.php it is possible to find vulnerable targets with Google Hacking.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

• WordPress Plugin

Vendor

• Ladela

Name

• Bookly Plugin

Version

• 27.0
• 27.1
• 27.2
• 27.3
• 27.4
• 27.5
• 27.6
• 27.7

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion