dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-57778

MEDIUM · 5.3 CVSS v3.1 Published 2026-07-13
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 5 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
Missing Authorization vulnerability in wpdevart Booking calendar, Appointment Booking System booking-calendar allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Booking calendar, Appointment Booking System: from n/a through <= 3.2.36.

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

This is a Missing Authorization vulnerability in the wpdevart Booking Calendar WordPress plugin. The plugin fails to properly enforce access control checks, allowing users to exploit incorrectly configured security levels. This could permit unauthenticated or low-privilege users to access functionality they should not have permission to use.

MitigationImplement proper authorization checks (capability checks in WordPress) on all sensitive functions and AJAX endpoints. Ensure all administrative functions verify user capabilities before executing. Update to the latest patched version if available.

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. Confirm wpdevart Booking Calendar is installed
    Navigate to WordPress Admin > Plugins and look for 'wpdevart Booking Calendar' in the installed plugins list. Note whether the plugin is active or inactive.
    Affected if The plugin is installed and active in WordPress
  2. Identify the plugin version
    In the Plugins list, click on the plugin name or view the plugin files. The version is typically displayed in the plugin header comment in the main PHP file (often named like wpdevart-booking-calendar.php). Compare this version against any official security advisories for CVE-2026-57778.
    Affected if The installed version matches or falls within the affected version range for this CVE
  3. Check for exposed AJAX endpoints
    Examine the plugin directory (usually wp-content/plugins/wpdevart-booking-calendar) for AJAX action handlers. Look in the main plugin file and any includes subfolders for calls to add_action('wp_ajax_...') or add_action('wp_ajax_nopriv_...'). The vulnerability exists if sensitive functions can be triggered via these public-facing AJAX hooks without capability verification.
    Affected if The plugin exposes AJAX endpoints that can be accessed without proper capability checks, especially those registered with wp_ajax_nopriv_
  4. Inspect admin function access controls
    Review the plugin PHP files for capability checks. Look for functions that perform administrative tasks (like modifying bookings, accessing settings, or managing data) and verify they include current_user_can() or similar WordPress capability checks before execution. Check files in the admin/ or includes/ directories for sensitive operations.
    Affected if Administrative functions or AJAX handlers lack current_user_can() or equivalent authorization checks before executing sensitive operations

You are affected if the wpdevart Booking Calendar plugin is active, the installed version falls within the vulnerable range, and the plugin exposes administrative functions or AJAX endpoints without proper capability verification.

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

Implement proper authorization checks (capability checks in WordPress) on all sensitive functions and AJAX endpoints. Ensure all administrative functions verify user capabilities before executing. Update to the latest patched version if available.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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