Wp Hotel BookingWordPress extension · Thimpress
CVE-2024-51582
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 · uneditedPath Traversal: '.../...//' vulnerability in ThimPress WP Hotel Booking wp-hotel-booking allows PHP Local File Inclusion.This issue affects WP Hotel Booking: from n/a through <= 2.2.9.
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 confidencePath traversal vulnerability using '.../...//' sequence in the WP Hotel Booking plugin allows attackers to perform Local File Inclusion (LFI) to include arbitrary PHP files from the server, potentially leading to code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Wp Hotel BookingWordPress extension
<= 2.1.4CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Verify WP Hotel Booking plugin is installedCheck your WordPress plugins directory or use WP-CLI: wp plugin list --name='wp-hotel-booking' or inspect the file system at wp-content/plugins/wp-hotel-booking/Affected if The plugin directory exists and contains WP Hotel Booking files
-
Determine installed plugin versionCheck the plugin header in wp-content/plugins/wp-hotel-booking/wp-hotel-booking.php for 'Version:' value, or use WP-CLI: wp plugin get wp-hotel-booking --field=versionAffected if Version is 2.1.4 or lower
-
Identify file inclusion endpointsSearch plugin source code for include, require, or file_get_contents calls that use user-supplied parameters (look for $_GET, $_POST, or similar in file inclusion functions)Affected if The plugin processes file path parameters without proper sanitization
-
Check for path traversal in access logsSearch web server access logs (usually in /var/log/nginx/ or /var/log/apache2/) for requests containing the sequence '.../...//' targeting PHP files, for example: grep -E '\.\./\.\./' /var/log/apache2/access.logAffected if Log entries show requests with the '.../...//' traversal pattern to PHP files on your site
Your environment is affected if WP Hotel Booking plugin version is 2.1.4 or lower and the plugin exposes file inclusion functionality that can be reached by unauthenticated users.
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.
dbcve · scopedUpgrade WP Hotel Booking to a patched version that implements proper input sanitization and blocks directory traversal sequences in file path parameters.
Latest version of WP Hotel Booking (newer than 2.2.9)
- 1. Navigate to the WordPress admin dashboard for the site running WP Hotel Booking
- 2. Go to Plugins > Installed Plugins
- 3. Locate WP Hotel Booking in the plugin list
- 4. Check if an update is available and update to the latest version
- 5. Alternatively, download the latest version from the official WordPress plugin repository or from ThimPress website
- 6. After updating, verify the plugin is functioning correctly on the booking system
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Wp Hotel Booking
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-51582 — 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-51582 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