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

5.3
Authorization Bypass Through User-Controlled Key
CVE CVE-2026-5234
CVSS 5.3 (Medium)
Publicly Published April 16, 2026
Last Updated April 17, 2026
Researcher normaandersonfrank

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.

References

Share

Vulnerability Details for Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress

Software Type Plugin
Software Slug latepoint (view on wordpress.org)
Patched? Yes
Remediation Update to version 5.4.0, or a newer patched version
Affected Version
  • <= 5.3.2
Patched Version
  • 5.4.0

Recent vulnerabilities in Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress

# Title CVE ID CVSS Researchers Date
1 LatePoint <= 5.3.2 - Authenticated (Contributor+) Stored Cross-Site Scripting via Shortcode Attributes CVE-2026-5391 6.4 alex_henry20 August 5, 2026
2 Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress <= 5.6.3 - Unauthenticated SQL Injection CVE-2026-57714 7.5 daroo July 8, 2026
3 LatePoint - Calendar Booking Plugin for Appointments and Events <= 5.4.0 - Unauthenticated Stripe PaymentIntent Amount-Binding Bypass CVE-2026-5356 7.5 Andrés Cruciani July 7, 2026
4 LatePoint <= 5.6.1 - Missing Authorization to Unauthenticated Arbitrary Customer Data Modification via process_step_customer() Booking Form Customer Step CVE-2026-11398 5.3 hhhai July 2, 2026
5 LatePoint <= 5.6.2 - Unauthenticated Insecure Direct Object Reference to Arbitrary Creation via 'service_id' Parameter CVE-2026-12657 5.3 gidget smith July 1, 2026
6 LatePoint <= 5.6.3 - Authenticated (Custom+) Privilege Escalation to Administrator via 'order[customer_id]' Parameter CVE-2026-13228 8.8 d.v4n_s3c June 30, 2026
7 LatePoint <= 5.6.2 - Cross-Site Request Forgery CVE-2026-11866 4.3 Meher Sudhakar Abbireddi June 25, 2026
8 LatePoint <= 5.5.1 - Authenticated (Agent+) Privilege Escalation to Administrator via IDOR in OsOrdersController::create_or_update + Unauthenticated Customer-Cabinet Password Reset CVE-2026-8176 7.5 d.v4n_s3c June 15, 2026
9 LatePoint <= 5.6.0 - Cross-Site Request Forgery via invoices__change_status Action CVE-2026-9719 4.3 alex_henry20 June 5, 2026
10 LatePoint – Calendar Booking Plugin for Appointments and Events <= 5.5.1 - Authenticated (Contributor+) Privilege Escalation CVE-2026-49083 8.8 VanTastic June 5, 2026

Did you know Wordfence Intelligence provides free personal and commercial API access to our comprehensive WordPress vulnerability database, along with a free webhook integration to stay on top of the latest vulnerabilities added and updated in the database? Get started today!

Learn more

Want to get notified of the latest vulnerabilities that may affect your WordPress site?
Install Wordfence on your site today to get notified immediately if your site is affected by a vulnerability that has been added to our database.

Get Wordfence

The Wordfence Intelligence WordPress vulnerability database is completely free to access and query via API. Please review the documentation on how to access and consume the vulnerability data via API.

Documentation