Read the docs

Sensitive data exposure in Bookly scheduling plugin for WordPress

Priority LOW 30CWE-200Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
Low
Impact type
Information disclosure
Confidentiality · integrity · availability
Low · None · None
Fix status
No fix listed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-200.

Summary

The Bookly (Online Scheduling and Appointment Booking System) plugin for WordPress through 28.4 exposes stored customer data. Its bookly_render_details endpoint loads a customer record from a phone number or email supplied in the request, without an identity check (CWE-200). An unauthenticated attacker who knows a registered customer's phone or email can read that customer's stored name, email, phone and internal notes when the Details step shows client placeholders.

Written with Claude Haiku 5.5 from the sources below · 2026-10-29

Description from the CNA

The Bookly – Online Scheduling and Appointment Booking System plugin for WordPress is vulnerable to Sensitive Information Exposure in versions up to, and including, 28.4 via the classic booking form's Details step. The endpoint bookly_render_details is registered for both wp_ajax and wp_ajax_nopriv, the module overrides csrfTokenValid() to always return true, and Bookly\Frontend\Components\Booking\InfoText::getCodes() calls UserBookingData::getCustomer() to load the persisted Customer entity keyed solely by the attacker-supplied phone (or email) with no invocation of the plugin's own customerIdentityConfirmed() predicate. When a site owner has placed the supported {client_name}, {client_email}, {client_phone}, or {client_note} placeholders into the Details step's Appearance information text, the matched customer's stored name, email, phone and internal notes are substituted into the returned HTML. This makes it possible for unauthenticated attackers who know only a registered customer's primary phone (or email) to read that customer's stored personal data.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.0028 20th percentileScored 2026-11-07
Fix No fix listed No fixed version in the sources yet

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
Yes
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
ladelaOnline Scheduling and Appointment Booking System – Booklyup to 28.4—No fix listedCNA
  • Online Scheduling and Appointment Booking System – Bookly Vendorladela Affected up to 28.4 Fixed in — No fix listed CNA

Remediation

The sources list no fixed version for Bookly (Online Scheduling and Appointment Booking System).

Written with Claude Haiku 5.5 from the sources below · 2026-10-29

Timeline

  1. 2026-10-10 Threatist record created from CVE-2026-103365
  2. 2026-10-10 Alias added: GHSA-5p6p-rjcr-26xj
  3. 2026-10-11 CISA SSVC decision points changed

References

  • TI-2026-62969 Authorization bypass in ladela Online Scheduling and Appointment Booking System – Bookly CVSS 3.1CRITICAL 9.1
  • TI-2026-60359 Authorization bypass in ladela Online Scheduling and Appointment Booking System – Bookly CVSS 3.1HIGH 7.5
  • TI-2026-12256 Online Scheduling and Appointment Booking System <= 27.5 - Unauthenticated SQL Injection CVSS 3.1HIGH 7.5
  • TI-2026-11363 Cross-site scripting in ladela Online Scheduling and Appointment Booking System – Bookly CVSS 3.1HIGH 7.2
  • TI-2026-04830 Cross-site scripting in ladela Online Scheduling and Appointment Booking System – Bookly CVSS 3.1HIGH 7.2
  • TI-2026-70141 PHP object injection in Bookly WordPress scheduling plugin CVSS 3.1HIGH 7.2
See all 12 →

Sources