CVE-2026-73347

TrueBooker – Appointment Booking and Scheduler System <= 1.2.6 - Unauthenticated Privilege Escalation

2026-08-19 00:00
Abdullah Kareem "cyberkareem"

Strategic Overview

Status
Patched in 1.2.7
Affected Plugin
TrueBooker – Appointment Booking and Scheduler System
Affected Version
<= 1.2.6
CVSS
7.3High
Weakness type
CWE-269 · Improper Privilege Management
CVE
CVE-2026-73347
View all TrueBooker – Appointment Booking and Scheduler System vulnerabilities

At a glance

CVE-2026-73347 is a high-severity Improper Privilege Management vulnerability in the TrueBooker WordPress plugin, affecting versions <= 1.2.6. It carries a CVSS score of 7.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.2.7; sites on affected versions should update now. Disclosed August 2026, reported by Abdullah Kareem "cyberkareem".

Vulnerability Overview

The TrueBooker – Appointment Booking and Scheduler System plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 1.2.6. This is due to insufficient restriction on the capabilities a user may grant themselves. This makes it possible for unauthenticated attackers to elevate their privileges beyond those intended for their role.

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.

CWE-269: Improper Privilege Management

Reaching this weakness in TrueBooker <= 1.2.6 takes no account at all. Improper privilege management means the code lets an account end up with capabilities its role should not have.

It converts a low-privileged account into an administrative one, which makes every other restriction on the site irrelevant. For TrueBooker the fix is 1.2.7: builds <= 1.2.6 are affected, anything from 1.2.7 onward is not.

Remediation

Update to version 1.2.7, 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.7 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-73347https://www.wordfence.com/threat-intel/vulnerabilities/id/caf5bdc7-8ed9-4b3f-a46d-511f021292a1https://nvd.nist.gov/vuln/detail/CVE-2026-73347

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C