CVE-2026-1431
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 · uneditedThe Booking Calendar plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the wpbc_ajax_WPBC_FLEXTIMELINE_NAV() function in all versions up to, and including, 10.14.13. This makes it possible for unauthenticated attackers to retrieve booking information including customer names, phones and emails.
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 · high confidenceThe Booking Calendar WordPress plugin has a broken access control vulnerability in the wpbc_ajax_WPBC_FLEXTIMELINE_NAV() AJAX function, which lacks a capability check. This allows unauthenticated attackers to query the function and retrieve sensitive booking data including customer names, phone numbers, and email addresses.
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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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.
-
Verify Booking Calendar plugin is installedIn WordPress admin, navigate to Plugins > Installed Plugins and locate 'Booking Calendar' in the list. Alternatively, check if the /wp-content/plugins/booking directory exists on the server.Affected if The Booking Calendar plugin is not present in the WordPress installation
-
Determine installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins and click on the Booking Calendar plugin to view its version number. Compare this against the fixed version 10.14.14.Affected if The installed version is lower than 10.14.14
-
Test AJAX endpoint for unauthenticated accessSend a POST request to wp-admin/admin-ajax.php with the parameter action=wpbc_flextimeline_nav, without providing any authentication tokens or cookies. Observe the response.Affected if The request returns booking data (customer names, phone numbers, email addresses) or does not return an authentication error
-
Inspect the vulnerable AJAX function codeIn the plugin files, locate the function wpbc_ajax_WPBC_FLEXTIMELINE_NAV() and verify whether it includes a capability check such as current_user_can() at the beginning.Affected if The function exists but lacks a capability check (e.g., current_user_can('manage_options')) before processing the request
A user is affected if the Booking Calendar plugin is installed with a version lower than 10.14.14 and the AJAX endpoint wpbc_flextimeline_nav is accessible without authentication.
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.
dbcve · scopedUpdate the Booking Calendar plugin to version 10.14.14 or later. If no update is available, manually add a capability check (e.g., current_user_can('manage_options')) to the vulnerable AJAX function.
Version higher than 10.14.13 (contact vendor for exact patched release)
- Log in to WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Locate the Booking Calendar plugin
- Check the current version installed
- If the installed version is 10.14.13 or lower, update the plugin to the latest available version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-1431 — 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-1431 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