CVE-2025-7038 json
LatePoint <= 5.1.94 - Unauthenticated Authentication Bypass via load_step Function
published 2025-09-30 13 mo ago modified 2026-06-17 4 mo ago also EUVD-2025-31703
- cvss
- 8.2
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 35%
- public exploits
- 0
- none known
Summary
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.
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 13 mo ago
Exploit prediction
0.41% chance of exploitation in the next 30 days, higher than 35% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.2 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N |
Affected products
- latepoint LatePoint – Calendar Booking Plugin for Appointments and Events
Classification
- Weakness
-
- CWE-288 Authentication Bypass Using an Alternate Path or Channel
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/d7389e17-a357-481a-8716-3a93cb6afa7c?source=cve
- wordpress.org /plugins/latepoint/#developers
- plugins.trac.wordpress.org /browser/latepoint/tags/5.1.93/latepoint.php
- plugins.trac.wordpress.org /browser/latepoint/tags/5.1.93/lib/controllers/steps_controller.php
- plugins.trac.wordpress.org /changeset?sfp_email=&sfph_mail=&reponame=&old=3366851%40latepoint&new=3366851%40latepoint&sfp_email=&sfph_mai
Sources
- CVE List CVE-2025-7038
- NVD CVE-2025-7038
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.