The Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress plugin for WordPress is vulnerable to Insecure Direct Object… (CVE-2026-91050)
Description
The Appointment Booking Plugin – LatePoint for WordPress versions up to and including 5.7.2 contains an Insecure Direct Object Reference (IDOR) vulnerability. This flaw allows unauthenticated attackers to manipulate booking parameters to create approved appointments linked to other customers' order items without proper authorization. The vulnerability arises because certain routes accept an order item ID parameter that is used without verifying ownership, payment status, or capacity. As a result, attackers can also access sensitive customer information such as names, email addresses, and order codes in booking confirmations.
CVSS v3.1
Score 4.3medium
Affected software
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in LatePoint plugin arises from insufficient authorization validation in the publicly accessible steps__start and steps__load_step routes. These routes accept a parameter presets[order_item_id] which is directly copied into the booking object without verifying ownership, payment status, or capacity. The is_bundle_scheduling() function only checks for the presence of order_item_id, bypassing proper validation. Consequently, unauthenticated attackers can create appointments on behalf of other customers and retrieve their personal data included in booking confirmations.
Potential Impact
An attacker can create approved appointments tied to other customers' order items without authentication, leading to unauthorized booking creation. Additionally, the attacker can read sensitive customer information such as names, email addresses, and order codes from booking confirmations. The vulnerability does not impact confidentiality of the booking system itself but leaks personal data and allows unauthorized booking manipulation.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict access to the affected routes if possible and monitor for suspicious booking activity. Avoid exposing the vulnerable parameters publicly and consider implementing custom authorization checks as a temporary measure.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-6mxr-h5c6-c7fc
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-91050"]
- Database Specific Severity
- MODERATE
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6acaadbe2cdf04f6565152c0
Added to database: 10/10/2026, 21:27:26 UTC
Last enriched: 10/10/2026, 21:42:11 UTC
Last updated: 10/11/2026, 03:48:07 UTC
Views: 9
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.