dbcve.org
Improper Privilege ManagementWeakness · CWE-269

CVE-2026-13228

HIGH · 8.8 CVSS v3.1 Published 2026-07-01
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 8 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 Privilege Escalation to Administrator in versions up to, and including, 5.6.3 This is due to an Insecure Direct Object Reference (IDOR) in the create_or_update() function of OsOrdersController, which allows an authenticated Agent to supply an arbitrary order[customer_id] and overwrite any LatePoint customer's email field (including one linked to a WordPress Administrator's account) through the public-scope customer set_data() call, combined with a missing role verification in OsAuthHelper::authorize_customer() which logs in the linked WordPress user without checking its role. This makes it possible for authenticated attackers, with custom (Agent)-level 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 · high confidence

The LatePoint WordPress plugin versions up to 5.6.3 contains an IDOR vulnerability in the create_or_update() function of OsOrdersController that allows authenticated Agent-level users to supply an arbitrary order[customer_id] and overwrite any customer's email, including Administrator accounts. Combined with missing role verification in OsAuthHelper::authorize_customer() that logs in the linked WordPress user without checking its role, this enables privilege escalation from Agent to Administrator.

MitigationUpdate the LatePoint plugin to version 5.6.4 or later which includes proper authorization checks and role verification. If unable to update immediately, restrict Agent-level user creation or monitor for suspicious account modifications.

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. Verify LatePoint plugin installation and version
    In WordPress admin, go to Plugins > Installed Plugins and find LatePoint, or check the plugin header in wp-content/plugins/latepoint/class.php for 'Version:' value
    Affected if Plugin version is 5.6.3 or earlier (versions up to 5.6.3 are affected)
  2. Confirm Agent-level user accounts exist
    In WordPress admin, go to Users and look for users with 'Agent' role (provided by LatePoint plugin), or query wp_usermeta for meta_key='latepoint_agent'
    Affected if Any Agent-level user accounts exist in the WordPress installation
  3. Inspect recent order modifications for customer_id tampering
    Query the latepoint_orders table in the database for records where order_customer_id does not match the user_id of the agent who created/modified the order, or check OsOrdersController create_or_update audit logs if available
    Affected if Orders exist with customer_id values different from the creating agent's user ID (indicates potential IDOR exploitation)
  4. Review WordPress user account modifications by Agent users
    Check WordPress activity logs or user modification logs for changes to Administrator or other privileged user emails performed by Agent-level accounts
    Affected if Any Administrator account email changes were made by Agent-level users

The environment is affected if LatePoint plugin version is 5.6.3 or earlier AND any Agent-level user accounts exist in the 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 LatePoint plugin to version 5.6.4 or later which includes proper authorization checks and role verification. If unable to update immediately, restrict Agent-level user creation or monitor for suspicious account modifications.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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