Skip to main content
VulnerabilityPublished

CVE-2026-5356: LatePoint (WordPress plugin) · Missing Authorization

Affects LatePoint (WordPress plugin)Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.5 High.

Data as of 21 Nov 2026, 17:35 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 30% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 21 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
latepointLatePoint – Calendar Booking Plugin for Appointments and EventsAffected
  • <=5.4.0
Fixed in–

AI-suggested

Until an official fix is available, users should monitor for updates from the LatePoint plugin vendor. Avoid using versions up to and including 5.4.0 in environments where payment integrity is critical. Consider disabling the Stripe Connect payment processor integration if feasible until a fix is released.

Description

The 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.

References

Community reviews

Loading reviews…