dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2026-12657

MEDIUM · 5.3 CVSS v3.1 Published 2026-07-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click 7 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The LatePoint WordPress plugin fails to validate authorization on the service_id parameter, allowing unauthenticated attackers to bypass access controls and create bookings for admin/agent-restricted services. The vulnerability exists in two AJAX endpoints (steps__load_step and steps__start) that accept user-controlled service identifiers without verifying the user has permission to access those specific services.

MitigationAdd server-side authorization checks to verify the requesting user has permission to book the specified service before processing bookings. Validate that service_id references a service the current user context is allowed to access, and reject unauthorized requests.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm LatePoint plugin is installed
    In WordPress admin, navigate to Plugins > Installed Plugins and look for 'LatePoint' in the list. Alternatively, check the /wp-content/plugins/ directory for a latepoint folder.
    Affected if LatePoint plugin is installed and active
  2. Check the installed LatePoint version
    In WordPress admin, go to Plugins > Installed Plugins, find LatePoint, and note the version number displayed. Compare this against any version information from the vendor.
    Affected if A version of LatePoint is installed (the vulnerability exists in the plugin code regardless of version)
  3. Test unauthenticated access to vulnerable AJAX endpoints
    Send a POST request to /wp-admin/admin-ajax.php with action=steps__load_step and a service_id parameter, without including any authentication cookies or headers. Also test action=steps__start. Use a tool like curl or Burp Suite.
    Affected if The endpoints respond without requiring authentication (response 200 instead of 401/403)
  4. Verify booking creation without proper authorization
    Submit a booking request via the affected AJAX endpoints using a service_id that should be restricted to admins or agents, without authenticating as a user with those privileges. Check if the booking is created successfully.
    Affected if Bookings can be created for admin/agent-restricted services without authentication or proper authorization tokens
  5. Review booking logs for unauthorized access
    In WordPress admin, navigate to LatePoint > Bookings and examine recent bookings. Look for entries created at times you did not make, or with user IDs that do not correspond to legitimate authenticated users.
    Affected if Bookings exist that were created without corresponding user authentication records

Your environment is affected if LatePoint is installed and the AJAX endpoints steps__load_step or steps__start accept unauthenticated requests to create bookings for restricted services.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Add server-side authorization checks to verify the requesting user has permission to book the specified service before processing bookings. Validate that service_id references a service the current user context is allowed to access, and reject unauthorized requests.

Recommended fix Moderate confidence

Plugin version 5.6.3 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the LatePoint – Calendar Booking Plugin for Appointments and Events
  4. 4. Check the current installed version (should be 5.6.2 or earlier)
  5. 5. Update the plugin to the latest available version (5.6.3 or later)
  6. 6. Verify the update was successful by confirming the new version number

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-12657 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-12657 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data