dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-14146

MEDIUM · 5.3 CVSS v3.1 Published 2026-01-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
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
The Booking Calendar plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 10.14.10 via the `WPBC_FLEXTIMELINE_NAV` AJAX action. This is due to the nonce verification being conditionally disabled by default (`booking_is_nonce_at_front_end` option is `'Off'` by default). When the `booking_is_show_popover_in_timeline_front_end` option is enabled (which is the default in demo installations and can be enabled by administrators), it is possible for unauthenticated attackers to extract sensitive booking data including customer names, email addresses, phone numbers, and booking details.

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 confidence

The Booking Calendar plugin for WordPress exposes sensitive booking data (customer names, emails, phone numbers, booking details) via the WPBC_FLEXTIMELINE_NAV AJAX action. The vulnerability exists because nonce verification is disabled by default (booking_is_nonce_at_front_end option is 'Off'), and when the booking_is_show_popover_in_timeline_front_end option is enabled (default in demo installations), unauthenticated attackers can directly query the AJAX endpoint to extract PII from bookings.

MitigationEnable nonce verification by setting 'booking_is_nonce_at_front_end' to 'On' in plugin settings, and disable 'booking_is_show_popover_in_timeline_front_end' if not required; also update to version 10.14.11 or later when available.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Booking Calendar plugin is installed
    Navigate to WordPress admin > Plugins and verify 'Booking Calendar' is active, or check the file wp-content/plugins/booking/booking.php for version info
    Affected if Plugin is installed and version is below 10.14.11
  2. Check nonce verification setting
    Query the WordPress database: SELECT option_value FROM wp_options WHERE option_name = 'booking_is_nonce_at_front_end'; or check via Settings > Booking Calendar > Advanced settings
    Affected if Option value is 'Off' or not set (default vulnerable state)
  3. Check timeline popover setting
    Query: SELECT option_value FROM wp_options WHERE option_name = 'booking_is_show_popover_in_timeline_front_end'; or check via plugin timeline settings
    Affected if Option value is 'On' (enabled by default in demo installations)
  4. Verify AJAX endpoint accessibility
    Send a POST request to /wp-admin/admin-ajax.php with action=WPBC_FLEXTIMELINE_NAV and check if booking data is returned without authentication
    Affected if Endpoint returns PII (customer names, emails, phone numbers) without requiring authentication or valid nonce

User is affected if Booking Calendar version is below 10.14.11 AND the booking_is_nonce_at_front_end option is 'Off' AND the booking_is_show_popover_in_timeline_front_end option is enabled, allowing unauthenticated PII exposure via the AJAX endpoint.

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

Enable nonce verification by setting 'booking_is_nonce_at_front_end' to 'On' in plugin settings, and disable 'booking_is_show_popover_in_timeline_front_end' if not required; also update to version 10.14.11 or later when available.

Recommended fix Moderate confidence

Booking Calendar version 10.14.11 or later

  1. 1. Navigate to the WordPress admin dashboard and go to Plugins > Installed Plugins
  2. 2. Locate the Booking Calendar plugin
  3. 3. Check the current version number - if it is 10.14.10 or below, an update is required
  4. 4. Update the Booking Calendar plugin to the latest available version (10.14.11 or higher)
  5. 5. After updating, verify that the booking_is_nonce_at_front_end option is set to 'On' in the plugin settings under Booking > Settings > General (or similar)
  6. 6. Confirm the booking_is_show_popover_in_timeline_front_end option is disabled unless specifically needed for business functionality

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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