WP Hotel Booking <= 2.0.7 - Missing Authorization to (Subscriber+) Arbitrary Post Deletion
Strategic Overview
- Status
- Patched in 2.0.8
- Affected Plugin
- WP Hotel Booking
- Affected Version
<= 2.0.7- CVSS
- 6.5Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2023-5651
At a glance
CVE-2023-5651 is a medium-severity Missing Authorization vulnerability in the WP Hotel Booking WordPress plugin, affecting versions <= 2.0.7. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high integrity impact). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 2.0.8; sites on affected versions should update now. Disclosed October 2023, reported by Krzysztof Zając.
Vulnerability Overview
The WP Hotel Booking plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the tp_extra_package_remove() function hooked via AJAX in all versions up to, and including, 2.0.7. This makes it possible for authenticated attackers, with subscriber-level access and above, to delete arbitrary posts.
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
WP Hotel Booking <= 2.0.7 carries this weakness at tp_extra_package_remove(), and reaching it 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. For WP Hotel Booking the fix is 2.0.8: builds <= 2.0.7 are affected, anything from 2.0.8 onward is not.
Remediation
Update to version 2.0.8, or a newer patched version
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. None of that substitutes for the fix: WP Hotel Booking 2.0.8 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in WP Hotel Booking
- 10.0CVE-2024-3605: WP Hotel Booking <= 2.1.0 SQL Injection
CVE-2024-3605 - 9.8CVE-2023-5652: WP Hotel Booking <= 2.0.7 SQL Injection
CVE-2023-5652 - 9.8CVE-2020-29047: WP Hotel Booking <= 1.10.3 Remote Code Execution
CVE-2020-29047 - 8.8CVE-2024-51582: WP Hotel Booking <= 2.2.9 Local File Inclusion
CVE-2024-51582 - 8.8CVE-2024-7855: WP Hotel Booking <= 2.1.2 Arbitrary File Upload
CVE-2024-7855 - 8.8CVE-2021-36852: WP Hotel Booking <= 1.10.5 Cross-Site Request Forgery
CVE-2021-36852 - 6.5CVE-2026-15153: WP Hotel Booking < 2.3.2 SQL Injection
CVE-2026-15153 - 6.5WP Hotel Booking Improper Authorization on Multiple REST API Routes
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C