CVE-2026-27405
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 Magepeople inc. WpBookingly allows Exploiting Incorrectly Configured Access Control Security Levels. This issue affects WpBookingly: from n/a through 1.2.9.
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 WpBookingly WordPress plugin by Magepeople. The plugin fails to properly enforce authorization checks on certain functions or endpoints, allowing authenticated attackers to access functionality or data beyond their intended privilege level due to incorrectly configured access control security levels.
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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify WpBookingly plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'WpBookingly' by Magepeople, or check the /wp-content/plugins/ directory for the wpbookingly folderAffected if The plugin is installed and active
-
Identify the installed versionCheck the plugin version number in the WordPress plugin list, or read the main plugin file header for the Version: fieldAffected if The version cannot be confirmed as patched or is within an affected version range
-
Check for subscriber-level or low-privilege user accountsIn WordPress admin, go to Users and review user roles. Pay particular attention to users with Subscriber, Customer, or custom low-privilege roles that should have limited accessAffected if Low-privilege authenticated users exist in the system
-
Verify capability enforcement on sensitive functionsInspect the plugin PHP files for missing current_user_can() or capability checks before sensitive operations like booking management, appointment scheduling, or admin functionsAffected if Sensitive plugin functions lack proper capability verification checks
-
Test access from low-privilege accountUsing a subscriber or limited role account, attempt to access plugin admin functions or sensitive endpoints (e.g., /wp-admin/admin.php?page=wpbookingly) to confirm unauthorized access is possibleAffected if A low-privilege user can access protected plugin functionality they should not be able to reach
If WpBookingly by Magepeople is installed and low-privilege authenticated users can access admin or sensitive plugin functions without proper capability checks, the environment is affected by this broken access control vulnerability.
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 dataImplement proper capability checks, role verification, and nonce validation on all sensitive functions within the plugin. Update to the latest patched version when released by the vendor.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2026-27405 — 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-27405 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