CVE-2026-5234: LatePoint <= 5.3.2 - Insecure Direct Object Reference to Unauthenticated Sensitive Financial Data Exposure via Sequential Invoice ID
latepoint · LatePoint – Calendar Booking Plugin for Appointments and Events
Affected: LatePoint – Calendar Booking Plugin for Appointments and Events · Exploitation: unlikely (under 1%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 53% of scored CVEs
DescriptionCVE.org
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.
Affected products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- latepoint · LatePoint – Calendar Booking Plugin for Appointments and Eventsup to and including 5.3.2
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Unlikely (under 1%). EPSS under 1%, or no score yet.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Weakness
- Insecure Direct Object Reference
- Vendor
- latepoint
- Published
- April 2026
CoverageNo articles yet
No CyberSIXT article names CVE-2026-5234 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.
References
- NVD entrynvd.nist.gov
- CVE recordcve.org
- Weakness CWE-639cwe.mitre.org
- wordfence.com/threat-intel/vulnerabilities/id/afec4c8c-a18d-4907wordfence.com
- plugins.trac.wordpress.org/browser/latepoint/trunk/lib/controlleplugins.trac.wordpress.org
- plugins.trac.wordpress.org/browser/latepoint/tags/5.2.9/lib/contplugins.trac.wordpress.org
- plugins.trac.wordpress.org/browser/latepoint/trunk/lib/controlleplugins.trac.wordpress.org
- plugins.trac.wordpress.org/browser/latepoint/tags/5.2.9/lib/contplugins.trac.wordpress.org
- plugins.trac.wordpress.org/browser/latepoint/trunk/lib/controlleplugins.trac.wordpress.org
- plugins.trac.wordpress.org/browser/latepoint/tags/5.2.9/lib/contplugins.trac.wordpress.org
- plugins.trac.wordpress.org/browser/latepoint/trunk/lib/controlleplugins.trac.wordpress.org
- plugins.trac.wordpress.org/browser/latepoint/tags/5.2.9/lib/contplugins.trac.wordpress.org
- plugins.trac.wordpress.org/changeset/3505127/latepoint/trunk/libplugins.trac.wordpress.org