dbcve.org
Path TraversalWeakness · CWE-22

CVE-2023-26526

HIGH · 7.7 CVSS v3.1 Published 2024-05-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
83/100
Remediation priority · High
Remotely reachable Zero-click

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 · unedited
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Nota-Info Bookly allows Path Traversal, Manipulating Web Input to File System Calls.This issue affects Bookly: from n/a through 21.7.1.

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 confidence

A path traversal vulnerability in Bookly allows attackers to manipulate web inputs to access files outside the intended directory scope. This improper limitation of pathname to a restricted directory enables unauthorized file system access through crafted path sequences.

MitigationUpgrade Bookly to version 21.7.2 or later to obtain the vendor patch. Until patched, implement strict input validation on all file path parameters and restrict filesystem permissions.

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
Low
User interaction
None
Scope
Changed
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Bookly plugin is installed
    Check if the Bookly plugin directory exists in your WordPress installation at wp-content/plugins/ (look for folder names containing 'bookly'). If using WordPress admin, navigate to Plugins > Installed Plugins and look for 'Bookly Responsive Appointment Booking Tool'.
    Affected if Bookly plugin is present in the WordPress installation
  2. Identify installed Bookly version
    In WordPress admin, go to Plugins > Installed Plugins > Bookly Responsive Appointment Booking Tool and read the version number displayed. Alternatively, open wp-content/plugins/bookly-responsive-appointment-booking-tool/readme.txt and check the 'Stable tag' line, or inspect the main plugin PHP file header for 'Version:' comment.
    Affected if Version is lower than 21.7.2 or the version cannot be determined (treat as vulnerable)
  3. Check for public-facing file download/upload endpoints
    Examine the Bookly plugin files (particularly in /backend/, /frontend/, or /common/ directories) for PHP files that handle file path parameters such as 'file', 'path', 'filename', 'download', or 'template'. Common vulnerable patterns include: require/include statements using user-supplied paths, file_get_contents($_GET['file']), or similar. Use grep to search: grep -r '$_GET' wp-content/plugins/bookly-responsive-appointment-booking-tool/ | grep -i 'file\|path\|download'
    Affected if Bookly exposes any frontend-accessible endpoints that accept file path parameters without sanitization
  4. Review access logs for path traversal attempts
    Examine web server access logs (usually in /var/log/apache2/access.log, /var/log/nginx/access.log, or WordPress debug logs) for suspicious request patterns targeting Bookly endpoints. Look for sequences like '../', '..\', URL-encoded variants (%2e%2e%2f), or requests to sensitive files (wp-config.php, /etc/passwd). Search: grep -E '\.\./|\.\.\\' /var/log/apache2/access.log | grep -i bookly
    Affected if Logs show path traversal attempts (../ sequences) targeting Bookly endpoints, indicating possible exploitation attempts

The environment is affected if Bookly Responsive Appointment Booking Tool is installed with a version lower than 21.7.2 AND the plugin exposes frontend file handling endpoints accessible to unauthenticated users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Bookly to version 21.7.2 or later to obtain the vendor patch. Until patched, implement strict input validation on all file path parameters and restrict filesystem permissions.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-26526 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-26526 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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