CVE-2026-48881: TrueBooker Appointment Booking broken access control

CVE-2026-48881 · Severity: critical · CVSS 9.1 · Published 2026-06-15

TrueBooker is a WordPress plugin used for managing appointment bookings. A security flaw allows unauthorized individuals to bypass security checks and perform actions that should be restricted to administrators. This could lead to the theft of sensitive customer data or unauthorized changes to the website's booking system.

Vendors: TrueBooker.

Quick answers

Is CVE-2026-48881 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-48881 being exploited in the wild.
How severe is CVE-2026-48881?
Critical severity, with a CVSS score of 9.1, published 15 June 2026.
Which products and versions are affected?
TrueBooker <= 1.1.9.
Is there a fix for CVE-2026-48881?
A patch was published on 2026-06-02: Version 1.2.0 released and advisory published by Patchstack Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-48881 attacked?
It is attacked over the network, in a web application.
Am I affected by CVE-2026-48881?
Check whether you run TrueBooker at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The TrueBooker plugin for WordPress (versions 1.1.9 and below) suffers from a broken access control vulnerability due to missing authorization checks (CWE-862). An unauthenticated remote attacker can exploit this flaw by sending crafted requests to vulnerable functions that fail to validate user permissions or nonces. Successful exploitation allows the attacker to execute high-privileged actions, potentially leading to full data compromise or unauthorized modification of site settings. The issue is resolved in version 1.2.0.

Affected products

  • TrueBooker TrueBooker Appointment Booking <= 1.1.9

Timeline

  • 2026-05-18: other: Reported by researcher Vincent Sevkli
  • 2026-06-02: patched: Version 1.2.0 released and advisory published by Patchstack
  • 2026-06-15: advisory: CVE published in NVD

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.