Horizon Alert
Summary of the vulnerability and why it matters
This advisory concerns a critical security vulnerability in the WP Booking System plugin for WordPress. The flaw allows authenticated users with basic access to delete any calendar notes within the system, potentially disrupting scheduling and data integrity. The main concern is confirming relevance and exposure of this plugin within our WordPress environment.
- Authenticated users can delete any calendar notes.
- Protects scheduling data integrity and operational continuity.
- Confirm plugin use and assess impact.
Attack Path
How an attacker could exploit the issue
An attacker can leverage this vulnerability by first gaining access to a WordPress site as a user with a Subscriber role or higher. With this access, they can then interact with the booking calendar's AJAX functionality to send a request to the `wpbs_action_ajax_calendar_remove_note()` function. This function, lacking a proper check for user permissions, will then delete arbitrary calendar notes, impacting data integrity and availability.
- Authenticated access required.
- Arbitrary deletion of calendar notes.
- Unauthorized data modification and loss.
Live Threat
Current exploitation, exposure, and threat context
This vulnerability could allow authenticated users with low-level access to delete any calendar notes within the booking system. This occurs when the system fails to properly check user permissions before executing a function designed to remove calendar notes.
- Calendar notes could be deleted.
- Notes may be removed by unauthorized users.
- Calendar data integrity is compromised.
Operational Fix
Recommended remediation, mitigation, and detection steps
For this vulnerability in the WP Booking System plugin, the application owner and the web infrastructure team are likely responsible for remediation. The first practical step is to identify all WordPress instances running the affected plugin, determine if they are externally accessible or host critical business data, and then assign ownership to the relevant team for risk-based remediation planning.
- Application owners should own the issue.
- Verify plugin reachability and critical data.
- Plan remediation based on verified risk.