LatePoint Plugin up to 5.3.2 on WordPress Error Message create_payment_intent_for_transaction transaction_intent_key authorization

Summaryinfo

A vulnerability was found in LatePoint Plugin up to 5.3.2 on WordPress. It has been classified as critical. This issue affects the function OsStripeConnectController::create_payment_intent_for_transaction of the component Error Message Handler. Performing a manipulation of the argument transaction_intent_key results in authorization. This vulnerability is cataloged as CVE-2026-5234. It is possible to initiate the attack remotely. There is no exploit available.

Detailsinfo

A vulnerability was found in LatePoint Plugin up to 5.3.2 on WordPress. It has been classified as critical. This affects the function OsStripeConnectController::create_payment_intent_for_transaction of the component Error Message Handler. The manipulation of the argument transaction_intent_key with an unknown input leads to a authorization vulnerability. CWE is classifying the issue as CWE-639. The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

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.

The weakness was shared by darkestmode. It is possible to read the advisory at wordfence.com. This vulnerability is uniquely identified as CVE-2026-5234 since 03/31/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 04/17/2026).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-23356). Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Type

• WordPress Plugin

Name

• LatePoint Plugin

Version

• 5.3.0
• 5.3.1
• 5.3.2

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Be aware that VulDB is the high quality source for vulnerability data.

Discussion