CVE-2026-6741
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 · uneditedThe LatePoint – Calendar Booking Plugin for Appointments and Events plugin for WordPress is vulnerable to Privilege Escalation in versions up to and including 5.4.1. This is due to a missing authorization check in the execute() method of the connect-customer-to-wp-user ability, which only requires the customer__edit capability granted to the latepoint_agent role by default, without verifying whether the target WordPress user ID belongs to a privileged account. This makes it possible for authenticated attackers with the latepoint_agent role to link any LatePoint customer record to an administrator's WordPress account and subsequently reset the administrator's password via the normal customer password-reset flow, resulting in full site takeover.
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 confidenceThe LatePoint booking plugin for WordPress has a privilege escalation vulnerability in versions up to 5.4.1. The connect-customer-to-wp-user ability's execute() method lacks authorization checks, only requiring the customer__edit capability granted to the latepoint_agent role. Attackers with this role can link any customer record to a privileged WordPress user (like administrator) and then use the standard password-reset flow to take over that account, achieving full site compromise.
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm LatePoint plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'LatePoint' or check the file /wp-content/plugins/latepoint/latepoint.php for the version numberAffected if LatePoint plugin is installed and running
-
Check installed LatePoint version against vulnerable rangeOpen /wp-content/plugins/latepoint/latepoint.php and locate the 'Version:' comment or header; compare the version number to any known patched version (the vulnerability exists in versions lacking proper authorization in the connect-customer-to-wp-user execute() method)Affected if The installed version lacks the patched authorization fix for the connect-customer-to-wp-user ability
-
Verify latepoint_agent role exists with customer__edit capabilityRun a WordPress user role query (via WP CLI: wp role list --fields=name or inspect wp_options for role keys) or use a role editor plugin to examine the latepoint_agent role capabilitiesAffected if The latepoint_agent role exists and includes the customer__edit capability
-
Identify users with latepoint_agent roleQuery WordPress users with the latepoint_agent role using: wp user list --role=latepoint_agent or database query on wp_usermeta for meta_key='wp_capabilities' containing 'latepoint_agent'Affected if There are one or more user accounts assigned the latepoint_agent role (especially untrusted or compromised accounts)
-
Check if connect-customer-to-wp-user ability is enabledInspect LatePoint settings in wp_options table for option_name containing 'latepoint_settings' or 'latepoint_capabilities', or examine the plugin code for the connect-customer-to-wp-user ability configurationAffected if The connect-customer-to-wp-user ability is enabled in the LatePoint capability settings
A user is affected if LatePoint is installed, the latepoint_agent role with customer__edit capability exists, and the connect-customer-to-wp-user ability is enabled, allowing a latepoint_agent user to link customers to admin accounts and perform password resets for full site takeover.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade to a patched version of the LatePoint plugin that adds proper authorization validation to ensure only non-privileged users can be linked to customer records, or restrict the latepoint_agent role's permissions until a patch is available.
5.4.2 or later (latest stable version)
- 1. Update the LatePoint – Calendar Booking Plugin for Appointments and Events plugin to the latest available version.
- 2. If automatic updates are not enabled, manually upload the updated plugin via WordPress admin > Plugins > Add New > Upload Plugin.
- 3. After updating, verify that the latepoint_agent role permissions have been properly scoped and no longer allow customer-to-WordPress-user linking.
- 4. Review all user accounts with the latepoint_agent role and revoke access for any untrusted users.
- 5. Consider resetting passwords for administrator-level WordPress accounts as a precautionary measure.
- 6. Monitor the site for any unauthorized changes or password reset requests.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,992.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-6741 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-6741 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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