CVE-2026-5356 latepoint CVE debrief

Who should care

Users of the LatePoint plugin for WordPress should be aware of this vulnerability and take steps to protect their sites. This includes updating the plugin to a version that fixes the vulnerability, monitoring for suspicious payment activity, and implementing additional security measures to prevent unauthorized payments. Site administrators, security teams, and operators of WordPress installations with the LatePoint plugin should prioritize this vulnerability and take immediate action to mitigate potential exposure.

Technical summary

The LatePoint plugin for WordPress is vulnerable to Improper Input Validation due to its Stripe Connect payment processor accepting a client-supplied PaymentIntent ID. This allows unauthenticated attackers to pay an arbitrary amount by supplying a previously succeeded PaymentIntent token. The vulnerability has a CVSS score of 7.5 and a severity of HIGH. Users of the LatePoint plugin for WordPress should be aware of this vulnerability and take steps to protect their sites. The vulnerability affects all versions up to, and including, 5.4.0.

Defensive priority

High

Recommended defensive actions

• Update the LatePoint plugin to a version that fixes the vulnerability
• Monitor for suspicious payment activity
• Implement additional security measures to prevent unauthorized payments
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record was published on 2026-07-08T13:16:56.767Z and has not been modified since then. The NVD entry is currently Deferred. There is limited information available about the vulnerability, and defenders should verify the affected scope and severity with the vendor. The plugin's Stripe Connect payment processor accepting a client-supplied PaymentIntent ID allows unauthenticated attackers to pay an arbitrary amount by supplying a previously succeeded PaymentIntent token. Defenders should review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.

Official resources