dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-1537

MEDIUM · 5.3 CVSS v3.1 Published 2026-02-12
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

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 unauthorized access of data due to a missing capability check on the load_step() function in all versions up to, and including, 5.2.6. This makes it possible for unauthenticated attackers to view booking information including customer names, email addresses, phone numbers, appointment times, and service details.

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 booking plugin has a broken access control vulnerability in the load_step() function, missing a capability check that allows unauthenticated users to access booking records containing customer PII (names, emails, phone numbers, appointment times, and service details). This is a classic IDOR/Insecure Direct Object Reference combined with missing authorization.

MitigationUpdate to the patched version of LatePoint (5.2.7 or later) which adds proper capability verification to the load_step() function. If an update is unavailable, consider disabling the plugin or implementing web server-level access restrictions.

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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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
    Locate the LatePoint plugin directory in your WordPress installation (typically under wp-content/plugins/latepoint) or check the Plugins page in WordPress admin panel for an active plugin named 'LatePoint'
    Affected if The LatePoint plugin is present in the WordPress installation
  2. Identify installed LatePoint version
    Open the main plugin file (usually latepoint.php) and locate the version comment/header, or check the plugin version displayed in the WordPress admin Plugins list
    Affected if The installed version is lower than 5.2.7 (the patched version)
  3. Verify unauthenticated access to load_step endpoint
    Send a crafted HTTP request to the WordPress admin-ajax.php endpoint with the latepoint action parameter (e.g., ?action=latepoint_load_step&step=booking_details) without providing any authentication cookies or credentials, then examine if the response returns booking data
    Affected if The request returns booking records containing customer PII (names, emails, phone numbers, appointment times) without requiring login
  4. Confirm booking data exposure contains PII
    Inspect the response from the unauthenticated load_step request to verify it includes sensitive customer information such as full names, email addresses, phone numbers, appointment timestamps, or service details
    Affected if The response contains unencrypted customer PII without any authorization validation

A user is affected if LatePoint plugin versions below 5.2.7 are installed and the load_step() function is accessible without authentication, exposing customer booking data.

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

Update to the patched version of LatePoint (5.2.7 or later) which adds proper capability verification to the load_step() function. If an update is unavailable, consider disabling the plugin or implementing web server-level access restrictions.

Recommended fix Moderate confidence

Update to the latest version of LatePoint (version 5.2.7 or later)

  1. 1. Back up your WordPress database and files before making any changes.
  2. 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard.
  3. 3. Locate the LatePoint plugin and check the current version installed.
  4. 4. Update the LatePoint plugin to the latest available version (after 5.2.6) which should contain the authorization fix.
  5. 5. Verify the update was successful by confirming the new version number in the plugins list.
  6. 6. Test that the load_step() function now properly checks user capabilities before allowing access to booking data.

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $2,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-1537 — 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-1537 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