Read the docs

Privilege escalation in LatePoint plugin for WordPress

Priority MEDIUM 40CWE-269Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
None
Attack complexity
Low
Impact type
Privilege escalation
Confidentiality · integrity · availability
High · High · High
Fix status
No fix listed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-269.

Summary

The LatePoint Appointment Booking Plugin for WordPress is affected in all versions up to and including 5.7.3. The settings handler does not check the default customer role on the server (CWE-269), so it accepts administrator. An authenticated user with the settings__edit capability, such as a LatePoint agent or custom role, can set this role, and new self-registered customers then get administrator privileges.

Written with Claude Haiku 5.5 from the sources below · 2026-10-29

Description from the CNA

The Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 5.7.3. This is due to the `OsSettingsController::update()` handler iterating over attacker-supplied `settings` parameters without an allowlist of permitted setting names or values, and `OsSettingsHelper::prepare_value()` performing no role allowlist validation before persisting the `default_wp_role_for_customer` setting — a restriction that exists only in the UI dropdown and is never enforced server-side. This makes it possible for authenticated attackers holding a LatePoint role with the `settings__edit` capability (such as an agent or custom role) to overwrite the default WordPress role for new customers with `administrator`, causing any subsequently self-registered LatePoint customer account to be created with full WordPress administrator privileges. Exploitation requires that a WordPress administrator has granted the `settings__edit` capability to a LatePoint agent or custom role, and that a new customer account is registered through LatePoint after the malicious setting change is persisted.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00293 22nd percentileScored 2026-11-07
Fix No fix listed No fixed version in the sources yet

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Total

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
latepointAppointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPressup to 5.7.3—No fix listedCNA
  • Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress Vendorlatepoint Affected up to 5.7.3 Fixed in — No fix listed CNA

Remediation

The sources list no fixed version for Appointment Booking Plugin (LatePoint | Calendar & Scheduling for WordPress).

Written with Claude Haiku 5.5 from the sources below · 2026-10-29

Timeline

  1. 2026-10-10 Threatist record created from CVE-2026-104766
  2. 2026-10-10 Alias added: GHSA-h977-fppf-xgg7
  3. 2026-10-11 Priority changed: MEDIUM → LOW
  4. 2026-10-11 CISA SSVC decision points changed
  5. 2026-10-11 Priority changed: LOW → MEDIUM

References

  • TI-2024-08303 LatePoint <= 5.0.12 - Authentication Bypass CVSS 3.1CRITICAL 9.8
  • TI-2024-08274 LatePoint <= 5.0.11 - Unauthenticated Arbitrary User Password Change via SQL Injection CVSS 3.1CRITICAL 9.8
  • TI-2026-62628 Appointment Booking Plugin <= 5.7.0 - Unauthenticated Arbitrary Shortcode Execution via First/Last Name Field CVSS 3.1CRITICAL 9.1
  • TI-2024-02298 LatePoint Plugin <= 4.9.9 - Missing Authorization and Sensitive Information Exposure via IDOR CVSS 3.1CRITICAL 9.1
  • TI-2026-76047 Race condition in LatePoint plugin allows authentication bypass CVSS 3.1CRITICAL 9.1
  • TI-2026-41538 WordPress LatePoint plugin <= 5.6.3 - SQL Injection vulnerability CVSS 3.1CRITICAL 9.3
See all 47 →

Sources