dbcve.org
Improper Privilege ManagementWeakness · CWE-269

CVE-2026-1566

HIGH · 8.8 CVSS v3.1 Published 2026-03-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 privilege escalation via password reset in all versions up to, and including, 5.2.7. This is due to the plugin allowing users with a LatePoint Agent role, who are creating new customers to set the 'wordpress_user_id' field. This makes it possible for authenticated attackers, with Agent-level access and above, to gain elevated privileges by linking a customer to the arbitrary user ID, including administrators, and then resetting the password.

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 (versions up to 5.2.7) contains an authenticated privilege escalation vulnerability. Users with the LatePoint Agent role can set the 'wordpress_user_id' field when creating new customer accounts. Since Agents can arbitrarily associate a customer with any WordPress user ID (including administrators), they can subsequently trigger a password reset for that high-privilege account and gain unauthorized access.

MitigationUpgrade to version 5.2.8 or later which restricts the wordpress_user_id field to prevent Agents from arbitrarily linking customers to privileged WordPress users. Until patched, disable the LatePoint plugin or revoke Agent role permissions.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Identify LatePoint plugin installation and version
    Check WordPress plugins directory or wp-cli: 'wp plugin list' or inspect /wp-content/plugins/latepoint/version.php or the plugin main file header for version number
    Affected if LatePoint plugin is installed and version is 5.2.7 or lower
  2. Check for users with LatePoint Agent role
    Query WordPress users with role 'latepoint_agent' via wp-cli: 'wp user list --role=latepoint_agent' or inspect user roles in WordPress admin under Users section
    Affected if Any user account possesses the LatePoint Agent role
  3. Verify Agent role can access customer management
    Inspect LatePoint role capabilities - Agents have 'create_customers' and 'edit_customers' capabilities by default. Check via 'wp user meta list' on Agent users or inspect latepoint_roles capability settings in database
    Affected if Agent role retains permission to create or edit customer records (default configuration)
  4. Confirm wordpress_user_id field is exposed in customer forms
    Inspect customer creation/edit forms in LatePoint frontend or admin - the wordpress_user_id dropdown or field should be visible to Agent role users when managing customers
    Affected if The wordpress_user_id field is present and modifiable in customer forms accessible to Agents

You are affected if LatePoint plugin versions 5.2.7 or lower is installed AND at least one user with the LatePoint Agent role exists with ability to create or edit customers, as this allows arbitrary WordPress user association for privilege escalation.

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

Upgrade to version 5.2.8 or later which restricts the wordpress_user_id field to prevent Agents from arbitrarily linking customers to privileged WordPress users. Until patched, disable the LatePoint plugin or revoke Agent role permissions.

Recommended fix High confidence

Version 5.2.8 or later (any version higher than 5.2.7)

  1. 1. Backup your WordPress database and files before making any changes
  2. 2. Update the LatePoint – Calendar Booking Plugin for Appointments and Events to the latest available version
  3. 3. After updating, verify that the 'wordpress_user_id' field is no longer user controllable when creating or editing customers
  4. 4. Review user accounts to ensure no unauthorized privilege escalation has occurred
  5. 5. Consider resetting passwords for high-privilege users as a precautionary measure

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
17.0 hours of engineering $3,020
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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