Skip to main content
VulnerabilityPublished Updated

CVE-2025-7038: LatePoint (WordPress plugin) · Authentication Bypass Using an Alternate Path or Channel

Affects LatePoint (WordPress plugin)Source CVE Database V5

0

Not known to be exploited · CVSS 8.2 High.

Data as of 26 Oct 2026, 12:55 UTC

CVSS 3.1 base score
8.2High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 34% 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:H/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Sep 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
latepoint LatePoint – Calendar Booking Plugin for Appointments and EventsAffected
  • =0
Fixed in–

AI-suggested

Until an official fix is released, restrict access to the affected AJAX endpoint if possible and monitor for suspicious activity related to LatePoint plugin usage. Avoid exposing the plugin to untrusted networks. Follow vendor updates closely for an official patch or mitigation instructions.

Description

The LatePoint plugin for WordPress is vulnerable to Authentication Bypass due to insufficient identity verification within the steps__load_step route of the latepoint_route_call AJAX endpoint in all versions up to, and including, 5.1.94. The endpoint reads the client-supplied customer email and related customer fields before invoking the internal login handler without verifying login status, capability checks, or a valid AJAX nonce. This makes it possible for unauthenticated attackers to log into any customer’s account.

References

Community reviews

Loading reviews…