dbcve.org
CWE-288Weakness · CWE-288

CVE-2026-27389

CRITICAL · 9.8 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 →
100/100
Remediation priority · Urgent
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
Authentication Bypass Using an Alternate Path or Channel vulnerability in designthemes WeDesignTech Ultimate Booking Addon wedesigntech-ultimate-booking-addon allows Authentication Abuse.This issue affects WeDesignTech Ultimate Booking Addon: from n/a through <= 1.0.1.

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 critical authentication bypass vulnerability in the WeDesignTech Ultimate Booking Addon plugin (versions up to 1.0.1) allows attackers to circumvent authentication mechanisms through an alternate path or channel, enabling unauthorized access to administrative functions.

MitigationApply any available vendor security update immediately; if no patch exists, disable the plugin and implement alternative booking functionality until a patched version is released.

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Check plugin version via WordPress admin
    Log into WordPress admin dashboard, navigate to Plugins > Installed Plugins, locate 'WeDesignTech Ultimate Booking Addon', and read the version number displayed under the plugin name
    Affected if Version displayed is 1.0.1 or lower (including any sub-version like 1.0.0, 0.9.x, etc.)
  2. Check plugin version via filesystem
    Access the server via FTP or file manager, navigate to wp-content/plugins/ultimate-booking-addon or similar plugin folder name, open the main plugin PHP file, and read the 'Version' header in the plugin comment block
    Affected if Version header shows 1.0.1 or lower
  3. Verify plugin is active
    In WordPress admin under Plugins > Installed Plugins, confirm the plugin shows as 'Active' (not just installed but deactivated)
    Affected if Plugin status is Active and version is 1.0.1 or lower
  4. Confirm plugin installation directory
    List the wp-content/plugins/ directory to verify the exact folder name used for this plugin, as some variations may exist (such as 'ultimate-booking-addon', 'ultimate-booking', or similar)
    Affected if A folder matching this plugin is present and contains version 1.0.1 or lower

Your environment is affected if the WeDesignTech Ultimate Booking Addon plugin is installed, active, and running at version 1.0.1 or any earlier version.

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

Apply any available vendor security update immediately; if no patch exists, disable the plugin and implement alternative booking functionality until a patched version is released.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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