Strategic Overview
- Status
- Patched in 5.0.13
- Affected Plugin
- LatePoint Plugin
- Affected Version
<= 5.0.12- CVSS
- 9.8Critical
- Weakness type
- CWE-288 · Authentication Bypass Using an Alternate Path or Channel
- CVE
CVE-2024-8943
At a glance
CVE-2024-8943 is a critical-severity Authentication Bypass Using an Alternate Path or Channel vulnerability in the LatePoint Plugin WordPress plugin, affecting versions <= 5.0.12. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 5.0.13; sites on affected versions should update now. Disclosed September 2024, reported by István Márton.
Vulnerability Overview
The LatePoint plugin for WordPress is vulnerable to authentication bypass in versions up to, and including, 5.0.12. This is due to insufficient verification on the user being supplied during the booking customer step. This makes it possible for unauthenticated attackers to log in as any existing user on the site, such as an administrator, if they have access to the user id. Note that logging in as a WordPress user is only possible if the "Use WordPress users as customers" setting is enabled, which is disabled by default. The vulnerability is partially patched in version 5.0.12 and fully patched in version 5.0.13.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-288: Authentication Bypass Using an Alternate Path or Channel
Reaching this weakness in LatePoint Plugin <= 5.0.12 takes a caller who can reach the endpoint. Authentication bypass through an alternate path means the application has a second route to a protected action that skips the checks the primary route performs.
The protection on the main path becomes irrelevant, because the attacker simply uses the route that never asks. For LatePoint Plugin the fix is 5.0.13: builds <= 5.0.12 are affected, anything from 5.0.13 onward is not.
Remediation
Update to version 5.0.13, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: LatePoint Plugin 5.0.13 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in LatePoint Plugin
- 9.8CVE-2025-6715: LatePoint <= 5.1.93 Local File Inclusion
CVE-2025-6715 - 9.8CVE-2024-8911: LatePoint <= 5.0.11 Arbitrary User Password Change
CVE-2024-8911 - 9.1CVE-2024-2472: LatePoint Missing Authorization and Info Exposure
CVE-2024-2472 - 8.8CVE-2026-13228: LatePoint Privilege Escalation to Administrator
CVE-2026-13228 - 8.8CVE-2026-49083: LatePoint Privilege Escalation
CVE-2026-49083 - 8.8CVE-2026-6741: LatePoint Privilege Escalation to Administrator
CVE-2026-6741 - 8.8CVE-2026-1566: LatePoint <= 5.2.7 Privilege Escalation
CVE-2026-1566 - 8.8CVE-2025-7052: LatePoint <= 5.1.94 CSRF to Account Takeover
CVE-2025-7052
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C