TrueBooker <= 1.2.3 - Missing Authorization to Unauthenticated Arbitrary Password Reset via 'truebooker_wp_user_id'
Strategic Overview
- Status
- Patched in 1.2.4
- Affected Plugin
- TrueBooker – Appointment Booking and Scheduler System
- Affected Version
<= 1.2.3- CVSS
- 9.8Critical
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2026-14365
At a glance
CVE-2026-14365 is a critical-severity Missing Authorization vulnerability in the TrueBooker WordPress plugin, affecting versions <= 1.2.3. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 1.2.4; sites on affected versions should update now. Disclosed August 2026, reported by Nhien Pham (nhienit).
Vulnerability Overview
The TrueBooker – Appointment Booking and Scheduler System plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 1.2.3. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for unauthenticated attackers to change the password of arbitrary user accounts, including administrators, which can be leveraged to gain access to those accounts.
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 privileges on the target site, 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 TrueBooker <= 1.2.3 takes no account at all. 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 TrueBooker the fix is 1.2.4: builds <= 1.2.3 are affected, anything from 1.2.4 onward is not.
Remediation
Update to version 1.2.4, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: TrueBooker 1.2.4 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 TrueBooker – Appointment Booking and Scheduler System
- 10.0CVE-2024-6924: TrueBooker <= 1.0.3 SQL Injection
CVE-2024-6924 - 9.8CVE-2026-14364: TrueBooker Unauthenticated Arbitrary Password Reset
CVE-2026-14364 - 9.8CVE-2026-61951: TrueBooker Privilege Escalation
CVE-2026-61951 - 7.5CVE-2026-13161: TrueBooker <= 1.2.2 SQL Injection
CVE-2026-13161 - 7.5CVE-2026-61950: TrueBooker SQL Injection
CVE-2026-61950 - 4.3CVE-2025-47543: TrueBooker <= 1.0.7 Cross-Site Request Forgery
CVE-2025-47543 - 4.3CVE-2024-6925: TrueBooker <= 1.0.2 CSRF to Settings Update
CVE-2024-6925
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C