Booking Calendar – Event Calendar <= 1.0.2 - Missing Authorization
Strategic Overview
- Status
- Unpatched
- Affected Plugin
- Booking Calendar – Event Calendar
- Affected Version
<= 1.0.2- CVSS
- 7.1High
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE pending
At a glance
This record tracks a high-severity Missing Authorization vulnerability in the Booking Calendar WordPress plugin, affecting versions <= 1.0.2. It carries a CVSS score of 7.1 (reachable over the network; low attack complexity; high integrity impact). The root cause is a missing authorization check on a reachable function. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed October 2022.
Vulnerability Overview
The Booking Calendar plugin for WordPress is vulnerable to authorization bypass due to a missing capability check on several functions (including omnivo_calendar_ajax_events_settings_save and omnivo_calendar_ajax_omnivo_calendar_delete_shortcode) in versions up to, and including, 1.0.2. This makes it possible for authenticated attackers, with subscriber-level permissions and above, to invoke those functions leading to setting changes and shortcode deletion among other issues.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on integrity.
CWE-862: Missing Authorization
Reaching this weakness in Booking Calendar <= 1.0.2 takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. No fixed build of this plugin is recorded for Booking Calendar yet, so installs running <= 1.0.2 stay exposed until the vendor ships one.
Remediation
No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Booking Calendar – Event Calendar
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C