# CVE-2026-91050: Missing authorization in Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress

> Attackers can create unauthorized bookings and read sensitive customer data by manipulating order item IDs in the LatePoint WordPress plugin.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/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:** 10 Oct 2026
- **Updated:** 11 Oct 2026
- **Also known as:** GHSA-6mxr-h5c6-c7fc

## What is CVE-2026-91050?

CVE-2026-91050 is a medium-severity missing authorization vulnerability in Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress, published on 10 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress plugin for WordPress is vulnerable to Insecure Direct Object Reference / Missing Authorization in versions up to, and including, 5.7.2. This is due to the publicly reachable steps__start and steps__load_step routes accepting a params[presets][order_item_id] value that is copied verbatim into the booking object without verifying that the referenced order item belongs to the current customer, is a bundle item, is paid, or has remaining capacity — the is_bundle_scheduling() bundle discriminator is a mere !empty(order_item_id) truthiness check, and the code flow explicitly removes the customer and payment steps when this is truthy (the source even carries a TODO acknowledging the missing validation). This makes it possible for unauthenticated attackers to create approved appointments against other customers' order items and to read those customers' names, email addresses, and order codes returned in the booking confirmation.

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

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


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

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

## Is CVE-2026-91050 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-91050 is a medium-severity missing authorization vulnerability in Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress, published on 10 Oct 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-91050 in the wild and no public exploit code.

Affected product: Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress. 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-91050/ (Markdown: https://insights.sbomify.com/CVE-2026-91050/index.md)
```

## Sources

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

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