CVE-2026-5234
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe LatePoint WordPress plugin up to 5.3.2 has an IDOR vulnerability in the OsStripeConnectController::create_payment_intent_for_transaction action. This public endpoint (no auth required) loads invoices by sequential integer ID without access_key or ownership verification, unlike other invoice endpoints that use cryptographic UUIDs. Attackers can enumerate valid invoice IDs, create unauthorized transaction records with financial data, and leak Stripe client secrets and payment amounts.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify LatePoint plugin installation and versionCheck the WordPress plugins directory or wp-content/plugins/latepoint folder for the main plugin file (e.g., latepoint.php) and read the Version header. Alternatively, query the WordPress database: SELECT option_value FROM wp_options WHERE option_name = 'latepoint_version';Affected if The installed version is 5.3.2 or lower (the summary indicates the vulnerability exists up to 5.3.2)
-
Verify the vulnerable endpoint is publicly accessibleMake an unauthenticated HTTP request to the WordPress site at /?latepoint_api=stripe_connect&action=create_payment_intent_for_transaction (or the actual endpoint path used by the plugin's routing). Check if the server returns a response rather than a 401/403 authentication error.Affected if The endpoint responds without requiring authentication (the summary states this is a public endpoint with no auth required)
-
Inspect invoice ID format used by the pluginExamine the OsInvoicesController and OsStripeConnectController code files. Look for how invoice IDs are generated and passed to the create_payment_intent_for_transaction action. Determine if they use sequential integers (e.g., 1, 2, 3) instead of cryptographic UUIDs.Affected if Invoices use sequential integer IDs that can be enumerated, rather than secure UUIDs with access_key verification
-
Check if the action lacks ownership verificationReview the code in OsStripeConnectController::create_payment_intent_for_transaction to see if it verifies the requester owns the invoice or possesses a valid access_key before loading invoice data or creating payment intents. Compare this to other invoice endpoints in OsInvoicesController that do perform such verification.Affected if The create_payment_intent_for_transaction action loads invoices without verifying ownership or validating an access_key, unlike secure endpoints
A user is affected if they have LatePoint plugin version 5.3.2 or lower installed and the create_payment_intent_for_transaction endpoint is exposed without authentication, allowing invoice enumeration and unauthorized transaction creation.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedAdd authentication requirement or implement cryptographic UUID access_key verification for the create_payment_intent_for_transaction action, following the secure pattern used by other invoice-related endpoints in OsInvoicesController.
Latest version after 5.3.2 (check WordPress plugin repository for current stable release)
- 1. Check the current version of the LatePoint plugin installed on your WordPress site
- 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
- 3. Locate LatePoint and note the current version number
- 4. Visit the WordPress plugin repository or the official LatePoint website to check for available updates
- 5. If version 5.3.2 or earlier is installed, update to the latest available version that addresses this vulnerability
- 6. After updating, verify that the OsStripeConnectController::create_payment_intent_for_transaction action now requires authentication
- 7. Confirm that invoice access now properly uses the cryptographic UUID access_key like other invoice-related actions
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-5234 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-5234 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data