Radar sectionsDatabase
Check my site
WordPress plugin

LatePoint <= 5.6.2 — Unauthenticated Insecure Direct Object Reference to Arbitrary Creation via 'service_id' Parameter

CVE-2026-12657Published · Updated

Action summary

Affected: ≤5.6.2Update to 5.6.3 or newer

All remediation steps
Severity
Medium5.3
CVSS
5.3
CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
What does this vector mean?
AV:N Attack vector
Network
AC:L Attack complexity
Low
PR:N Privileges required
None
UI:N User interaction
None
S:U Scope
Unchanged
C:N Confidentiality
None
I:L Integrity
Low
A:N Availability
None
Weakness
CWE-639 Authorization Bypass Through User-Controlled Key
Required access
No account needed
Exploit prediction (EPSS)
No score
CISA KEV
Not listed

Am I affected?

Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress latepoint

  1. Affected≤ 5.6.2
  2. Patched in5.6.3

Update to 5.6.3 or newer.

You are affected if you run ≤ 5.6.2. Version 5.6.3 and later are not affected by this issue.

  • Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress.
  • No admin access? Run a passive check of your site. It reads public files only.
  • No account is needed to exploit this. Treat any exposed site on an affected version as at risk.

What to do

  1. Update to version 5.6.3, or a newer patched version
  2. Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
  3. Watch Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress to get an email when the next vulnerability is published.

Advisory

Source description from Wordfence Intelligence, credited to gidget smith.

The LatePoint – Calendar Booking Plugin for Appointments and Events plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 5.6.2 via the 'service_id' parameter due to missing validation on a user controlled key. This makes it possible for unauthenticated attackers to create approved bookings against services explicitly restricted to admins and agents, consuming restricted appointment capacity and triggering unauthorized bookings for admin/agent-only services. The bypass works via both the params[booking][service_id] parameter in steps__load_step and the presets[selected_service] parameter in steps__start, both of which are publicly accessible without authentication.

Exploits & references

Proof-of-concept & detection

No public proof-of-concept or detection template is known for this vulnerability.

Advisories & patches

More in Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress

All 59
More vulnerabilities in Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress
SeverityVulnerabilityCVEPublished
Critical9.1Unauthenticated Authentication Bypass via Account Takeover via 'IS NOT NULL' Sentinel in 'password_reset_token' Parameter
≤5.7.6Update to 5.7.7
CVE-2026-118066
Medium5.4Unauthenticated Stored Cross-Site Scripting via Customer Email Field
≤5.7.6Update to 5.7.7
CVE-2026-119152
Medium4.4Authenticated (Administrator+) Stored Cross-Site Scripting
≤5.7.5Update to 5.7.6
CVE-2026-105258
Medium5.3Unauthenticated Payment Bypass
≤5.7.4Update to 5.7.5
CVE-2026-105256
Medium4.3Authenticated (Agent+) Insecure Direct Object Reference
≤5.7.4Update to 5.7.5
CVE-2026-105257

Timeline

  1. CVE published

    Severity medium, CVSS 5.3

  2. Record last updated

Sources & licenses

Wordfence record
Vulnerability data
Wordfence Intelligence. Copyright 2012-2026 Defiant Inc. Licensed under the CC BY-SA 4.0.
CVE® identifiers
Copyright 1999-2026 The MITRE Corporation. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
CVSS / CWE
National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
VulnCrest content
Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.

How we use these sources

Search VulnCrest Radar

Are you sure?