Bookify <= 1.0.9 - Authenticated (Subscriber+) Privilege Escalation
Strategic Overview
- Status
- Patched in 1.0.10
- Affected Plugin
- Bookify – Appointment Booking & Scheduling for WordPress
- Affected Version
<= 1.0.9- CVSS
- 8.8High
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2025-48142
At a glance
CVE-2025-48142 is a high-severity Missing Authorization vulnerability in the Bookify WordPress plugin, affecting versions <= 1.0.9. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 1.0.10; sites on affected versions should update now. Disclosed July 2025, reported by Denver Jackson.
Vulnerability Overview
The Appointment Booking Plugin for WordPress | Efficient Booking, Calendar & Client Scheduling – Bookify plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 1.0.9. This is due to plugin missing capability checks on several REST API endpoints. This makes it possible for authenticated attackers, with Subscriber-level access and above, to create new user accounts with administrator privileges.
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 confidentiality, integrity, availability — full site compromise territory.
CWE-862: Missing Authorization
Reaching this weakness in Bookify <= 1.0.9 takes an account at Subscriber level or above. 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 Bookify the fix is 1.0.10: builds <= 1.0.9 are affected, anything from 1.0.10 onward is not.
Remediation
Update to version 1.0.10, 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: Bookify 1.0.10 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C