WordPress security changelog
MEDIUM CVE-2026-5234 Deferred

LatePoint – Calendar Booking Plugin for Appointments and Events: Broken access control

LatePoint – Calendar Booking Plugin for Appointments and Events is affected by broken access control. The vulnerable path is reachable without authentication. A successful request can reach data or an operation that should be restricted to another user or a more privileged role. The published affected range is <= 5.3.2.

CVE / CNA score 5.3 CVSS 3.1 · security@wordfence.com
NVD score Pending NVD has not published its own CVSS assessment.
Component
LatePoint – Calendar Booking Plugin for Appointments and Events
Plugin slug
latepoint
Affected
<= 5.3.2
Safe version
See mitigation notes
Published
Apr 17, 2026
Weakness
CWE-639 — Authorization Bypass Through User-Controlled Key

This CVE was published Apr 17, 2026 and is one of 32 known issues for this plugin.

What to do

Update, patch or deactivate.

No fixed release is identified. Update LatePoint – Calendar Booking Plugin for Appointments and Events when a release after 5.3.2 becomes available; until then, disable and remove it when the site's risk warrants. The official upstream changelog lists version 5.6.10, which is newer than the published affected range. Its changelog does not clearly confirm this specific fix, so it is not counted as a known-safe release.

No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

Source record

Technical description

The LatePoint plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 5.3.2. The vulnerability exists because the OsStripeConnectController::create_payment_intent_for_transaction action is registered as a public action (no authentication required) and loads invoices by sequential integer invoice_id without any access_key or ownership verification. This is in contrast to other invoice-related actions (view_by_key, payment_form, summary_before_payment) in OsInvoicesController which properly require a cryptographic UUID access_key. This makes it possible for unauthenticated attackers to enumerate valid invoice IDs via an error message oracle, create unauthorized transaction intent records in the database containing sensitive financial data (invoice_id, order_id, customer_id, charge_amount), and on sites with Stripe Connect configured, the response also leaks Stripe payment_intent_client_secret tokens, transaction_intent_key values, and payment amounts for any invoice.

CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

References

Primary and upstream sources