CVE-2025-14146
BaseFortify
Publication date: 2026-01-09
Last updated on: 2026-01-09
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| wordfence | booking_calendar | to 10.14.10 (inc) |
| wordfence | booking_calendar | 10.14.8 |
| wordfence | booking_calendar | 7.2.1.10 |
| wordfence | booking_calendar | 8.8.3.6 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-862 | The product does not perform an authorization check when an actor attempts to access a resource or perform an action. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The vulnerability in the Booking Calendar plugin for WordPress allows unauthenticated attackers to extract sensitive booking information such as customer names, email addresses, phone numbers, and booking details. This happens because the nonce verification, which is supposed to protect AJAX actions, is conditionally disabled by default due to the 'booking_is_nonce_at_front_end' option being set to 'Off'. When the 'booking_is_show_popover_in_timeline_front_end' option is enabled (default in demo installations and can be enabled by administrators), attackers can exploit the 'WPBC_FLEXTIMELINE_NAV' AJAX action to access this sensitive data without authentication.
How can this vulnerability impact me? :
This vulnerability can lead to sensitive information exposure, allowing attackers to access personal data of customers such as names, email addresses, phone numbers, and booking details without any authentication. This can result in privacy breaches, potential identity theft, phishing attacks, and loss of customer trust. Since the vulnerability is exploitable remotely via AJAX requests, it poses a significant risk to the confidentiality of booking data managed by the plugin.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring AJAX requests to the `WPBC_FLEXTIMELINE_NAV` action in the Booking Calendar plugin. Since the vulnerability involves unauthenticated AJAX requests extracting sensitive booking data due to disabled nonce verification, you can look for suspicious HTTP POST requests to the WordPress admin-ajax.php endpoint with the parameter `action=WPBC_FLEXTIMELINE_NAV`. Commands to detect such activity could include using network monitoring tools or command-line utilities like curl or wget to simulate or detect these requests. For example, you can use a command like: `curl -X POST -d 'action=WPBC_FLEXTIMELINE_NAV' https://yourwordpresssite.com/wp-admin/admin-ajax.php` and observe if sensitive booking data is returned without authentication. Additionally, monitoring web server logs for unauthenticated POST requests to admin-ajax.php with this action parameter can help detect exploitation attempts. However, no specific detection commands are provided in the resources. [6]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include enabling nonce verification on the front-end by setting the `booking_is_nonce_at_front_end` option to 'On' to ensure that AJAX requests like `WPBC_FLEXTIMELINE_NAV` require valid nonces, preventing unauthenticated access. Administrators should also review and disable the `booking_is_show_popover_in_timeline_front_end` option if it is enabled, as this option allows unauthenticated attackers to extract sensitive booking data. Updating the Booking Calendar plugin to a version later than 10.14.10 where nonce verification is properly enforced is recommended. Additionally, monitoring and restricting access to AJAX endpoints and applying web application firewall (WAF) rules to block suspicious requests targeting this AJAX action can help mitigate exploitation. [3, 6]