CVE-2026-91050 json
Appointment Booking Plugin <= 5.7.2 - Insecure Direct Object Reference to Authenticated (Subscriber+) Unauthorized Booking Creation and Sensitive Information Disclosure via 'params[presets][order_item_id]' Parameter
published 2026-10-10 30 d ago modified 2026-10-13 26 d ago also EUVD-2026-96085
- cvss
- 4.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 11%
- public exploits
- 0
- none known
Summary
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.
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 28 d ago
Exploit prediction
0.21% chance of exploitation in the next 30 days, higher than 11% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N |
Affected products
- latepoint Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress
Classification
- Weakness
-
- CWE-639 Authorization Bypass Through User-Controlled Key
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/136f8e94-a09a-48c4-bea9-e8b21d3fd91f?source=cve
- plugins.trac.wordpress.org /browser/latepoint/tags/5.6.11/lib/helpers/steps_helper.php#L1028
- plugins.trac.wordpress.org /browser/latepoint/tags/5.6.11/lib/helpers/steps_helper.php#L1281
- plugins.trac.wordpress.org /browser/latepoint/tags/5.6.11/lib/models/booking_model.php#L842
- plugins.trac.wordpress.org /browser/latepoint/tags/5.6.11/lib/helpers/steps_helper.php#L677
- plugins.trac.wordpress.org /browser/latepoint/tags/5.6.11/lib/helpers/steps_helper.php#L2350
- plugins.trac.wordpress.org /browser/latepoint/tags/5.6.11/lib/controllers/steps_controller.php#L17
- plugins.trac.wordpress.org /browser/latepoint/tags/5.6.11/lib/controllers/steps_controller.php#L341
Sources
- CVE List CVE-2026-91050
- NVD CVE-2026-91050
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.