dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2025-3769

MEDIUM · 5.3 CVSS v3.1 Published 2025-05-14
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

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 Insecure Direct Object Reference in all versions up to, and including, 5.1.92 via the 'view_booking_summary_in_lightbox' due to missing validation on a user controlled key. This makes it possible for unauthenticated attackers to retrieve appointment details such as customer names and email addresses.

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 before 5.1.93 contains an Insecure Direct Object Reference (IDOR) vulnerability in the 'view_booking_summary_in_lightbox' function. The function fails to validate a user-controlled key, allowing unauthenticated attackers to access arbitrary appointment records and retrieve sensitive customer PII such as names and email addresses.

MitigationUpdate the LatePoint plugin to version 5.1.93 or later which adds proper authorization validation to the booking summary endpoint to verify the requester has permission to view the requested booking data.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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. Identify LatePoint plugin installation
    In WordPress admin, go to Plugins > Installed Plugins and look for LatePoint, or check the file /wp-content/plugins/latepoint/ for the plugin directory
    Affected if LatePoint plugin is present on the WordPress site
  2. Determine installed LatePoint version
    Check the plugin header in /wp-content/plugins/latepoint/latepoint.php for the 'Version' field, or view the plugin details in WordPress admin plugins list
    Affected if Version is lower than 5.1.93 (e.g., 5.1.92, 5.1.0, 4.x, etc.)
  3. Verify the vulnerable endpoint exists
    Check if the file /wp-content/plugins/latepoint/vendor/selected-lightbox.php or similar lightbox handler exists and contains the 'view_booking_summary_in_lightbox' function
    Affected if The function exists in the codebase and is callable via the WordPress AJAX or front-end routes
  4. Test IDOR vulnerability
    Send a crafted request to the booking summary endpoint (typically /?latepoint_action=view_booking_summary_in_lightbox or WP AJAX) with an manipulated booking ID parameter without authentication
    Affected if The endpoint returns booking details (customer name, email) for arbitrary booking IDs without requiring authorization or ownership verification

A site is affected if LatePoint plugin version is below 5.1.93 AND the view_booking_summary_in_lightbox function is accessible without authentication, allowing unauthorized access to booking records and customer PII.

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

Update the LatePoint plugin to version 5.1.93 or later which adds proper authorization validation to the booking summary endpoint to verify the requester has permission to view the requested booking data.

Recommended fix Moderate confidence

Version 5.1.93 or later

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate the LatePoint plugin
  4. Check if an update is available and update to version 5.1.93 or later
  5. Alternatively, download the latest version from the WordPress plugin repository at wordpress.org/plugins/latepoint/

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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