dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-11398

MEDIUM · 5.3 CVSS v3.1 Published 2026-07-03
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 7 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 authorization bypass in all versions up to, and including, 5.6.1. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for unauthenticated attackers to modify the personally identifiable information (first name, last name, phone number, and notes) of any existing customer record, including those linked to administrator accounts, by submitting the booking form with a known customer's email address. Exploitation requires the plugin to be configured with guest bookings enabled (is_customer_auth_disabled() returning true), which is necessary for the vulnerable unauthenticated code path in process_step_customer() to be reached.

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 fails to properly authorize unauthenticated requests in its booking form processing. When guest bookings are enabled (is_customer_auth_disabled() returns true), the process_step_customer() function accepts any submitted email address and updates the corresponding customer record's PII (first name, last name, phone, notes) without verifying the requester owns or is authorized to modify that account.

MitigationDisable guest bookings in the plugin settings to prevent unauthenticated access, or apply any available security update from the vendor. If neither is immediately possible, consider restricting the booking form access via firewall rules until patched.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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. Verify LatePoint plugin is installed
    Check WordPress plugins directory or admin panel for LatePoint plugin presence and activation status
    Affected if Plugin is installed and active
  2. Confirm guest bookings are enabled
    Navigate to LatePoint settings or inspect the booking form configuration to verify is_customer_auth_disabled() returns true, which allows unauthenticated booking submissions
    Affected if Guest bookings setting is enabled (allows unauthenticated access to booking forms)
  3. Verify booking form is publicly accessible
    Test accessing the booking form page/shortcode without authentication to confirm it accepts submissions from unauthenticated users
    Affected if Booking form is accessible to unauthenticated visitors

If guest bookings are enabled and the booking form is publicly accessible, unauthenticated attackers can modify customer PII by submitting arbitrary email addresses through the booking form.

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

Disable guest bookings in the plugin settings to prevent unauthenticated access, or apply any available security update from the vendor. If neither is immediately possible, consider restricting the booking form access via firewall rules until patched.

Recommended fix Moderate confidence
  1. 1. Log in to WordPress admin dashboard
  2. 2. Navigate to LatePoint > Settings > General
  3. 3. Locate the 'Guest bookings' or 'Allow guest bookings' option
  4. 4. Disable/uncheck the guest bookings option to set is_customer_auth_disabled() to return false
  5. 5. Save the settings changes
  6. 6. Verify the setting has been applied by checking that unauthenticated users can no longer modify existing customer records through the booking form

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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