dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-27388

HIGH · 7.5 CVSS v3.1 Published 2026-03-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
Missing Authorization vulnerability in designthemes DesignThemes Booking Manager designthemes-booking-manager allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects DesignThemes Booking Manager: from n/a through <= 2.0.

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

A missing authorization vulnerability in the DesignThemes Booking Manager WordPress plugin allows unauthenticated or unauthorized users to access functionality that should require proper access control. The vulnerability stems from incorrectly configured access control security levels that fail to validate user permissions before executing sensitive operations.

MitigationImplement proper authorization checks (capability checks, nonce verification, role verification) on all sensitive plugin functions and AJAX endpoints to ensure only authorized users can access booking management features.

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
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 plugin presence
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'DesignThemes Booking Manager' in the list. Confirm whether the plugin is active.
    Affected if The plugin is installed and active in WordPress
  2. Identify plugin version
    In the plugins list, click on the plugin details link for DesignThemes Booking Manager and locate the version number displayed in the plugin metadata.
    Affected if The installed version is lower than any version containing the fix for missing authorization checks
  3. Inspect AJAX endpoint accessibility
    Use a tool like curl or Burp Suite to send requests to common WordPress AJAX endpoints (wp-admin/admin-ajax.php) with action parameters related to booking functions (such as booking_save, booking_update, or similar actions used by the plugin) without providing authentication credentials.
    Affected if Requests to booking-related AJAX actions complete successfully without requiring login or returning an authorization error
  4. Test unauthenticated booking operations
    Send HTTP requests to plugin endpoints that handle booking creation, modification, or deletion while not logged in or logged in as a subscriber-level user. Check if the operations execute without proper capability verification.
    Affected if Sensitive booking operations can be performed by unauthenticated or low-privilege users
  5. Review user role capabilities
    Create a test user with the lowest privilege role (such as Subscriber) and attempt to access booking management features through the plugin frontend or admin interface.
    Affected if A user with Subscriber role can access or modify booking data that should require higher privileges

The environment is affected if the DesignThemes Booking Manager plugin is installed and allows unauthenticated or unauthorized users to execute booking management functions without proper permission validation.

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

Implement proper authorization checks (capability checks, nonce verification, role verification) on all sensitive plugin functions and AJAX endpoints to ensure only authorized users can access booking management features.

Recommended fix Moderate confidence

Latest version above 2.0 (contact vendor for specific fixed release)

  1. Check the WordPress admin dashboard for updates to the DesignThemes Booking Manager plugin
  2. Update the plugin to the latest available version from the WordPress repository or DesignThemes
  3. If no update is available through WordPress, contact DesignThemes directly for the patched version
  4. Verify the update was successfully applied
  5. Test the booking functionality to ensure the plugin still works correctly after the update
Caveat Unknown - test in staging before production deployment

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

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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