Security Alert Summary
The Appointment Booking and Scheduler Plugin – Truebooker for WordPress contains a sensitive information exposure vulnerability in its view files that can allow unauthenticated users to directly access exposed PHP view files and view potentially sensitive information.
CVE Details
- CVE ID: CVE-2026-1797
- Affected component: The Appointment Booking and Scheduler Plugin – Truebooker plugin for WordPress
- Affected versions: All versions up to, and including, 1.1.4
- Published: March 31, 2026 at 5:16:10 AM
- Last modified: March 31, 2026 at 5:16:10 AM
- CVSS v3.1: Base Score 5.3, MEDIUM. Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
- Authentication / privileges / user interaction: No authentication or privileges required; no user interaction required (Unauthenticated, Privileges Required: NONE, User Interaction: NONE)
- Primary impact: Confidentiality: LOW; Integrity: NONE; Availability: NONE
- CWE: CWE-862
Technical Details
The plugin exposes view PHP files that can be directly accessed by unauthenticated users. According to the description, an attacker can retrieve potentially sensitive information by requesting exposed files in the plugin’s views directory. One referenced example path is main/views/truebooker-user.php, which indicates view templates are reachable without sufficient access checks. The vulnerability exists because the view files do not enforce authentication or authorization controls before rendering or exposing data. The impact is limited to information disclosure: attackers can read whatever data is present or rendered by those view files, but there is no indication of direct modification or denial of service from this issue.
How This Could Impact Your Website
In a typical site setup, an external unauthenticated actor could access exposed view files and discover information that relates to staff or users. For example, an attacker might obtain internal user email addresses or other details shown in a view template, which could increase the risk of targeted phishing or social engineering against the site owner, internal staff, or external contractors. The issue does not inherently permit modification of site content or take the site offline, but the disclosed information could be used as part of a broader social engineering campaign. If you’re unsure whether your site is affected or how to assess your current user roles and plugins, it may be worth having a professional review your setup.
Recommended Actions
- Update the affected plugin as soon as a patched version is available.
- Review and reduce unnecessary user roles, especially contributor-level accounts and other low-privilege users that may have data exposed by templates.
- Enforce strong passwords and two-factor authentication for editors and administrators.
- Remove unused or unmaintained plugins to reduce attack surface.
- Monitor site activity and access logs for unusual requests to plugin paths or direct requests to view files.
If you’d like help reviewing your plugins, user roles, or overall WordPress security posture, our team at Freshy is happy to help.