Skip to content

CVE-2026-5234 LatePoint <= 5.3.2 - Insecure Direct Object Reference to Unauthenticated Sensitive Financial Data Exposure via Sequential Invoice ID

MediumCVSS 5.3 EPSS 0.70%
Published
Updated
Exploit status
No public exploit known
CISA SSVC
No known exploitation · automatable: no · technical impact: partial
Technology
WordPress

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.

Upgrade path

2 packages: 2 fixed.

PackageAffectedFixed inStatus
LatePoint – Calendar Booking Plugin for Appointments and Events <= 5.3.2 after 5.3.2 Fixed
wordpress latepoint(WordPress) < 5.4.0 5.4.0 Fixed

Affected products

ProductAffected versionsFixed in
LatePoint – Calendar Booking Plugin for Appointments and Events <= 5.3.2 No fix listed
wordpress latepoint(WordPress) < 5.4.0 5.4.0

References