dbcve.org
Improper Privilege ManagementWeakness · CWE-269

CVE-2026-8176

HIGH · 7.5 CVSS v3.1 Published 2026-06-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
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 to Administrator in versions up to, and including, 5.5.1. The plugin chains three independent flaws that together allow an authenticated Agent (Agent+) to overwrite a WordPress Administrator's password without ever invoking an Administrator-only API. This makes it possible for authenticated attackers, with Agent access and above, to elevate their privileges to Administrator.

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 · moderate confidence

The LatePoint WordPress plugin up to version 5.5.1 contains a privilege escalation vulnerability where authenticated Agent users can chain three independent flaws to overwrite a WordPress Administrator's password without invoking any Administrator-only API. This allows Agents to elevate their privileges to full Administrator access.

MitigationUpdate the plugin to the latest version once available and reset all Administrator account passwords as a precaution. Until the patch is applied, consider restricting or monitoring Agent-level user accounts.

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

CVSS:3.1/AV:N/AC:H/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 if LatePoint plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for LatePoint, or check the /wp-content/plugins/ directory for the latepoint folder. Note the installed version from the plugin header.
    Affected if LatePoint plugin is present in the WordPress installation
  2. Confirm the installed version number
    Read the version number from the plugin metadata in the plugins list page or from the main plugin file header comment.
    Affected if The version is 5.5.1 or any version up to 5.5.1 (no patch version specified)
  3. Check if Agent user role exists in WordPress
    Go to Users > Users List in WordPress admin and look for users with the 'Agent' role, or query the wp_usermeta table for meta_value containing 'latepoint_agent' or 'lp_agent'.
    Affected if There are one or more users assigned the Agent role in the system
  4. Verify Agent users have access to LatePoint features
    Log in as an Agent user and navigate to the LatePoint dashboard area to confirm the role provides access to the plugin functionality.
    Affected if Agent users can access the LatePoint frontend or dashboard interface

You are affected if LatePoint plugin version 5.5.1 or lower is installed and active with Agent-level user accounts present in the WordPress system.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to the latest version once available and reset all Administrator account passwords as a precaution. Until the patch is applied, consider restricting or monitoring Agent-level user accounts.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,440
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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