CVE-2026-5356
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 – Calendar Booking Plugin for Appointments and Events plugin for WordPress is vulnerable to Improper Input Validation in all versions up to, and including, 5.4.0. This is due to the plugin's Stripe Connect payment processor accepting a client-supplied PaymentIntent ID. This makes it possible for unauthenticated attackers to pay an arbitrary amount by supplying a previously succeeded PaymentIntent token.
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 fails to validate that a Stripe PaymentIntent belongs to the current booking transaction before accepting it as payment. An unauthenticated attacker can supply a previously succeeded PaymentIntent ID from a legitimate transaction, allowing them to complete their own booking payment with an arbitrary amount.
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
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 installationCheck WordPress plugins directory for 'latepoint' folder, or use wp-cli: wp plugin list --status=active --format=csv | findstr latepointAffected if LatePoint plugin is installed and active
-
Determine installed LatePoint versionCheck plugin version in wp-content/plugins/latepoint/readme.txt or via WordPress admin: Plugins > LatePoint > View DetailsAffected if Version is unknown or unpatched (no specific version ranges provided; compare to any vendor advisories)
-
Verify Stripe integration is enabledCheck WordPress admin: LatePoint > Settings > Payments > Stripe. Confirm Stripe payment method is active.Affected if Stripe payment method is enabled in LatePoint settings
-
Inspect payment processing endpointReview the file handling Stripe PaymentIntent confirmation (typically in includes/controllers/ or similar). Look for code that processes $_POST['payment_intent_id'] or similar Stripe parameters without validating ownership to the current booking.Affected if Code processes Stripe PaymentIntent without booking transaction validation
-
Check for booking amount validationExamine payment processing logic for server-side verification that PaymentIntent amount matches booking total before marking payment complete.Affected if No server-side validation exists comparing PaymentIntent amount to booking amount
User is affected if LatePoint plugin with Stripe integration is active and the payment processing code does not validate that the supplied PaymentIntent belongs to the current booking transaction.
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.
From vendor dataImplement server-side validation to verify that the PaymentIntent matches the current booking's amount, customer, and status before processing payment confirmation.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-5356 — 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-5356 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