CVE-2026-27409
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 · uneditedMissing Authorization vulnerability in Webba Plugins Webba Booking allows Exploiting Incorrectly Configured Access Control Security Levels. This issue affects Webba Booking: from n/a through 6.4.13.
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 confidenceThis is a missing authorization (broken access control) vulnerability in the Webba Booking WordPress plugin. The plugin fails to properly verify user permissions before allowing access to certain functionality, allowing attackers to exploit incorrectly configured access control security levels to perform actions they shouldn't be authorized to perform.
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Webba Booking is installedNavigate to WordPress Admin > Plugins and look for 'Webba Booking' in the list of installed plugins, or check the /wp-content/plugins/ directory for the webba-booking folderAffected if The plugin is installed and active on the WordPress site
-
Identify the installed versionIn Plugins list, click 'View Details' on Webba Booking to see the version number, or read the main plugin PHP file header for the 'Version' tagAffected if The installed version is any release prior to when the authorization fix was implemented (compare to latest available version)
-
Check for exposed admin AJAX endpointsReview the plugin's PHP files in /wp-content/plugins/webba-booking/ for admin-ajax.php hooks (add_action('wp_ajax_...')) that perform sensitive operations without capability checks like 'manage_options'Affected if AJAX endpoints exist that lack current_user_can() or capability checks before executing privileged actions
-
Inspect REST API routes for authorization gapsSearch plugin code for register_rest_route() calls and verify each route includes permission_callback functions that validate user capabilitiesAffected if REST API routes exist that accept requests without verifying user authorization permissions
-
Test access from low-privilege userCreate or use a subscriber-level user account and attempt to access known Webba Booking admin functions directly via URL or AJAX calls (e.g., booking management, settings修改)Affected if A user without administrative privileges can successfully perform actions that should require elevated permissions
You are affected if Webba Booking is installed and low-privilege users can access administrative functions without proper capability verification.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate Webba Booking to the latest version which should contain proper authorization checks. If no update is available, audit the plugin code for all functional endpoints and add capability checks or nonce verification before executing privileged operations.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-27409 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-27409 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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