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

> Authenticated staff users can read other staff members' appointment details and customer PII by manipulating the appointment ID parameter.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** GHSA-j9h8-cf5v-78mc

## What is CVE-2026-12905?

CVE-2026-12905 is a medium-severity vulnerability in ladela Online Scheduling and Appointment Booking System – Bookly, published on 16 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-12905 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-12905 is a medium-severity vulnerability in ladela Online Scheduling and Appointment Booking System – Bookly, published on 16 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-12905 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-12905/ (Markdown: https://insights.sbomify.com/CVE-2026-12905/index.md)
```

## Sources

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

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