Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-2230: CWE-639 Authorization Bypass Through User-Controlled Key in wpdevelop Booking Calendar

0
Medium
VulnerabilityCVE-2026-2230cvecve-2026-2230cwe-639
Published: Wed Feb 18 2026 (02/18/2026, 16:28:14 UTC)
Source: CVE Database V5
Vendor/Project: wpdevelop
Product: Booking Calendar

Description

The Booking Calendar plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 10.14.14 via the handle_ajax_save function due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with Subscriber-level access and above, and booking permissions granted by an Administrator, to modify other users' plugin settings, such as booking calendar display options, which can disrupt the booking calendar functionality for the targeted user.

AI-Powered Analysis

AILast updated: 02/19/2026, 12:05:04 UTC

Technical Analysis

CVE-2026-2230 is an authorization bypass vulnerability categorized under CWE-639 (Authorization Bypass Through User-Controlled Key) found in the Booking Calendar plugin for WordPress, developed by wpdevelop. The flaw exists in the handle_ajax_save function, where the plugin fails to properly validate a key parameter controlled by the user. This lack of validation allows authenticated attackers with at least Subscriber-level access and granted booking permissions to manipulate other users' plugin settings. Specifically, attackers can alter booking calendar display options, which can disrupt the normal functioning of the booking calendar for the targeted user. The vulnerability affects all versions up to and including 10.14.14. The CVSS v3.1 base score is 4.3 (medium severity), reflecting that the attack vector is network-based, requires low attack complexity, privileges at the level of a logged-in user, no user interaction, and impacts integrity but not confidentiality or availability. No patches or known exploits are currently reported, but the vulnerability's presence in a widely used WordPress plugin poses a risk to organizations relying on this plugin for booking management. The flaw does not allow data disclosure or system compromise but can cause operational disruption by altering user-specific settings, potentially leading to confusion or denial of service at the application level.

Potential Impact

For European organizations, the primary impact is operational disruption of booking services managed via the Booking Calendar plugin. This can affect customer experience, appointment scheduling, and internal resource management, particularly in sectors like hospitality, healthcare, and professional services that rely heavily on booking systems. Since the vulnerability allows modification of plugin settings by unauthorized users with limited privileges, it can lead to inconsistent or incorrect calendar displays, potentially causing scheduling conflicts or loss of trust in the service. Although the vulnerability does not compromise sensitive data or system availability, the integrity of booking configurations is at risk. Organizations with multiple users having booking permissions are more vulnerable to insider threats or compromised accounts exploiting this flaw. The medium severity rating indicates a moderate risk, but the ease of exploitation by authenticated users makes it a concern for environments with many users or delegated permissions.

Mitigation Recommendations

To mitigate CVE-2026-2230, organizations should first audit and restrict booking permissions to the minimum necessary users, avoiding granting booking permissions broadly, especially to Subscriber-level users. Implement strict role-based access controls within WordPress to limit who can modify booking settings. Monitor user activity logs for unusual changes to booking calendar configurations. Since no patch is currently available, consider temporarily disabling the Booking Calendar plugin or replacing it with alternative booking solutions if feasible. Keep the plugin updated and apply any future patches promptly once released by wpdevelop. Additionally, implement multi-factor authentication (MFA) for all WordPress accounts to reduce the risk of compromised credentials being used to exploit this vulnerability. Regularly review plugin permissions and user roles to ensure compliance with the principle of least privilege.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2026-02-08T18:51:36.435Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6996fb478fb9188dea8c0328

Added to database: 2/19/2026, 12:00:07 PM

Last enriched: 2/19/2026, 12:05:04 PM

Last updated: 2/21/2026, 12:18:05 AM

Views: 5

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats