# CVE-2026-103365: Information disclosure in Online Scheduling and Appointment Booking System – Bookly

> Unauthenticated attackers can read stored customer personal data by exploiting a logic flaw in the booking details endpoint if specific placeholders are configured.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Oct 2026
- **Updated:** 11 Oct 2026
- **Also known as:** GHSA-5p6p-rjcr-26xj

## What is CVE-2026-103365?

CVE-2026-103365 is a medium-severity vulnerability in ladela Online Scheduling and Appointment Booking System – Bookly, published on 10 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-103365?


## How do I fix CVE-2026-103365?

No fix has been published for CVE-2026-103365 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-103365 being exploited?

There is no known exploitation of CVE-2026-103365 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-103365 and fix it if it is affected.

What it is: CVE-2026-103365 is a medium-severity vulnerability in ladela Online Scheduling and Appointment Booking System – Bookly, published on 10 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-103365 in the wild and no public exploit code.

Affected product: ladela Online Scheduling and Appointment Booking System – Bookly. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-103365/ (Markdown: https://insights.sbomify.com/CVE-2026-103365/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-103365
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-103365
- OSV: https://osv.dev/vulnerability/CVE-2026-103365

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-103365/
Summaries are generated and may contain mistakes; the official description above is the record.