CVE-2026-94432 Missing authorization in Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress
Unauthenticated attackers can enumerate invoices and modify transaction intents due to missing authorization checks in the LatePoint WordPress plugin.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-94432?
CVE-2026-94432 is a medium-severity missing authorization vulnerability in Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress, published on 2 Oct 2026. An attacker can exploit it over the internet without logging in, 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 in versions up to, and including, 5.7.1 via the OsPaypalConnectController::create_order_for_transaction() action registered as a public (unauthenticated) route through wp_ajax_nopriv_latepoint_route_call. The handler loads an OsInvoiceModel by a sequential integer 'invoice_id' with no access-key/UUID or ownership check (the sibling Stripe and Razorpay handlers require a 128-bit access-key UUID via OsInvoicesHelper::get_invoice_by_key), and then calls OsTransactionIntentHelper::create_or_update_transaction_intent() which persists a transaction intent tied to the target invoice's customer_id, order_id and charge_amount and regenerates its intent_key before the PayPal-configured guard is reached. This makes it possible for unauthenticated attackers to enumerate invoices belonging to arbitrary customers, create unauthorized transaction-intent rows linked to another customer's data, and overwrite the intent_key of any in-flight NEW-status transaction intent — invalidating the intent_key that legitimate Stripe/Razorpay flows are waiting on and breaking payment webhooks for those customers.
Weakness: CWE-639
Which versions are affected by CVE-2026-94432?
How do I fix CVE-2026-94432?
No fix has been published for CVE-2026-94432 yet. Limit exposure of the affected software until one is available.
Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.
Is CVE-2026-94432 being exploited?
There is no known exploitation of CVE-2026-94432 in the wild and no public exploit code.
Sources
Also known as GHSA-9rc5-84g4-qhvh.