CVE-2026-1797
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe Appointment Booking and Scheduler Plugin – Truebooker plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.1.4 through views php files. This makes it possible for unauthenticated attackers to view potentially sensitive information contained in the exposed views php files via direct access.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe Truebooker WordPress plugin exposes view PHP files directly via web access, allowing unauthenticated attackers to retrieve potentially sensitive information from these template files. The vulnerability exists because the views directory is accessible without proper access controls or server-side restrictions.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if Truebooker plugin is installedCheck the WordPress wp-content/plugins directory for a folder named 'truebooker' or search the plugins list via wp-adminAffected if The Truebooker plugin folder exists in the WordPress installation
-
Locate the views directoryNavigate to wp-content/plugins/truebooker and look for a 'views' or 'view' subdirectory containing PHP filesAffected if A views directory with PHP template files exists within the plugin
-
Test direct web access to view filesAttempt to access a view PHP file via HTTP request, for example: https://yoursite.com/wp-content/plugins/truebooker/views/somefile.phpAffected if The PHP file loads and displays content rather than being blocked or returning a 403 error
-
Check for sensitive data exposureExamine the response from accessed view files to see if they reveal configuration details, API keys, database credentials, or other sensitive informationAffected if The view files return actual PHP content, error messages, or sensitive data rather than being properly protected
-
Verify server-side access controlsCheck if .htaccess rules exist in the views directory to block direct access, or if the plugin uses defined('ABSPATH') checks at the top of view filesAffected if No .htaccess restrictions exist AND view files lack ABSPATH inclusion guards, allowing unauthenticated access
You are affected if the Truebooker plugin is installed and its view PHP files can be directly accessed via web browser without authentication or server-side restrictions.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataRestrict direct access to view files by moving them outside the web root or implementing proper access controls (e.g., .htaccess rules, checks for defined constants) to prevent direct PHP inclusion. Update to a patched version if available.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-1797 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-1797 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data