CVE-2024-38717
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 · uneditedImproper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Booking Ultra Pro allows PHP Local File Inclusion.This issue affects Booking Ultra Pro: from n/a through 1.1.13.
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 confidenceBooking Ultra Pro plugin versions through 1.1.13 contain a path traversal vulnerability allowing PHP Local File Inclusion (LFI). An attacker could exploit this by manipulating file path parameters to include arbitrary PHP files from the server, potentially achieving remote code execution.
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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/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.
-
Check Booking Ultra Pro plugin versionNavigate to WordPress admin > Plugins > Installed Plugins > Booking Ultra Pro, or inspect the main plugin file (typically /wp-content/plugins/booking-ultra-pro/core/class-*.php or similar) and look for the 'Version' header commentAffected if The installed version is 1.1.13 or lower (any version up to and including 1.1.13)
-
Identify file inclusion endpointsSearch plugin source files for PHP functions: include, require, include_once, or require_once used with variables (e.g., include($file), include($_GET['path']))Affected if The plugin contains dynamic file inclusion logic using user-controlled input without proper sanitization
-
Test for accessible file inclusion parametersIf file inclusion functions are found, review the plugin's admin or public PHP files for parameters that accept file paths (common names: file, path, template, page, include, load) and check if they are reachable without authenticationAffected if File path parameters are exposed and accept user input without validation (the vulnerability is exploitable)
-
Review server access logsInspect web server access logs (Apache/Nginx) for requests to the plugin containing path traversal patterns such as ../, ..\, or absolute paths like /etc/passwdAffected if Suspicious path traversal requests targeting the plugin appear in logs (indicates attempted exploitation)
A user is affected if their Booking Ultra Pro installation is version 1.1.13 or lower AND the vulnerable file inclusion functionality is accessible and accepts user-supplied paths.
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 dataUpgrade to the latest patched version of Booking Ultra Pro. If no patch is available, restrict file inclusion to allowed directories and implement strict input validation on all file path parameters.
- 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-2024-38717 — 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-2024-38717 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