CVE-2026-8176

LatePoint <= 5.5.1 - Authenticated (Agent+) Privilege Escalation to Administrator via IDOR in OsOrdersController::create_or_update + Unauthenticated Customer-Cabinet Password Reset

2026-06-15 20:57
d.v4n_s3c

Strategic Overview

Status
Patched in 5.5.2
Affected Version
<= 5.5.1
CVSS
7.5High
Weakness type
CWE-269 · Improper Privilege Management
CVE
CVE-2026-8176
View all Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress vulnerabilities

At a glance

CVE-2026-8176 is a high-severity Improper Privilege Management vulnerability in the Appointment Booking Plugin WordPress plugin, affecting versions <= 5.5.1. It carries a CVSS score of 7.5 (reachable over the network; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 5.5.2; sites on affected versions should update now. Disclosed June 2026, reported by d.v4n_s3c.

Vulnerability Overview

The LatePoint – Calendar Booking Plugin for Appointments and Events plugin for WordPress is vulnerable to Privilege Escalation to Administrator in versions up to, and including, 5.5.1. The plugin chains three independent flaws that together allow an authenticated Agent (Agent+) to overwrite a WordPress Administrator's password without ever invoking an Administrator-only API. This makes it possible for authenticated attackers, with Agent access and above, to elevate their privileges to Administrator.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-269: Improper Privilege Management

Reaching this weakness in Appointment Booking Plugin <= 5.5.1 takes no account at all. Improper privilege management means the code lets an account end up with capabilities its role should not have.

It converts a low-privileged account into an administrative one, which makes every other restriction on the site irrelevant. For Appointment Booking Plugin the fix is 5.5.2: builds <= 5.5.1 are affected, anything from 5.5.2 onward is not.

Remediation

Update to version 5.5.2, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Appointment Booking Plugin 5.5.2 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C