WP Hotel Booking <= 2.0.8 - Insufficient Authorization to Unauthorized Post Deletion
Strategic Overview
- Status
- Patched in 2.0.9
- Affected Plugin
- WP Hotel Booking
- Affected Version
<= 2.0.8- CVSS
- 4.3Medium
- Weakness type
- CWE-863 · Incorrect Authorization
- CVE
CVE-2023-5799
At a glance
CVE-2023-5799 is a medium-severity Incorrect Authorization vulnerability in the WP Hotel Booking WordPress plugin, affecting versions <= 2.0.8. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). The issue is fixed in version 2.0.9; sites on affected versions should update now. Disclosed October 2023, reported by Erwan LR.
Vulnerability Overview
The WP Hotel Booking plugin for WordPress is vulnerable to unauthorized modification of data due to insufficient authorization checks 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 contributor-level access and above, to delete arbitrary posts. While the patch for CVE-2023-5651 ensured subscriber-level users couldn't delete arbitrary posts, the checks were not sufficient in preventing higher authenticated users such as contributors from deleting 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.
CWE-863: Incorrect Authorization
WP Hotel Booking <= 2.0.8 carries this weakness at tp_extra_package_remove(), and reaching it takes a caller who can reach the endpoint. Incorrect authorization means a permission check exists but evaluates the wrong thing, so it passes for callers it was meant to stop.
The action runs for users the code intended to exclude, with the same effect as having no check at all. For WP Hotel Booking the fix is 2.0.9: builds <= 2.0.8 are affected, anything from 2.0.9 onward is not.
Remediation
Update to version 2.0.9, 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.9 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
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 - 7.5WP Hotel Booking <= 2.0.0 Settings Update
- 6.5CVE-2026-15153: WP Hotel Booking < 2.3.2 SQL Injection
CVE-2026-15153
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C