CVE-2025-66078
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 Control of Generation of Code ('Code Injection') vulnerability in jetmonsters Hotel Booking Lite motopress-hotel-booking-lite allows Remote Code Inclusion.This issue affects Hotel Booking Lite: from n/a through <= 5.2.3.
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 confidenceA code injection vulnerability in the motopress-hotel-booking-lite WordPress plugin allows remote attackers to inject and execute arbitrary code through improper control of code generation. The vulnerability stems from insufficient input validation on parameters used in dynamic code inclusion, enabling Remote Code Execution (RCE) without authentication.
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
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/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.
-
Confirm Hotel Booking Lite plugin is installedIn WordPress admin, navigate to Plugins > Installed Plugins and look for 'Hotel Booking Lite' or 'motopress-hotel-booking-lite'. Alternatively, check the wp-content/plugins directory for a folder containing 'hotel-booking' or 'motopress'.Affected if The plugin is present in the WordPress installation
-
Identify the installed plugin versionIn WordPress admin > Plugins, click 'View Details' on Hotel Booking Lite to see the version number. Alternatively, read the main plugin PHP file (usually plugin-root.php) and look for the 'Version' header in the plugin comment block.Affected if The version is 5.2.3 or lower
-
Search for dynamic code inclusion patterns in plugin filesUse grep or a file search to scan PHP files in the hotel-booking plugin directory for patterns like 'include($', 'require($', 'include_once($', 'require_once(' with variable parameters, especially where user input (GET/POST/REQUEST) parameters are passed directly to include/require statements.Affected if Dynamic includes using unsanitized input variables are found in the plugin code
-
Verify if the vulnerable endpoint is accessibleTest access to common dynamic inclusion endpoints by attempting requests with manipulated parameters. Check for PHP files that process $_GET, $_POST, or $_REQUEST parameters and use them in file inclusion operations without validation.Affected if Endpoints accepting dynamic file parameters without validation are accessible and respond to requests
-
Check for recent unauthorized code execution indicatorsReview web server access logs (Apache/nginx) for suspicious POST/GET requests to hotel-booking plugin files with unusual parameter values, especially attempts to include remote files or unexpected PHP file paths. Also check for new/modified PHP files in the plugin directory.Affected if Log analysis reveals requests attempting code injection or unexpected file inclusions targeting the plugin
A user is affected if Hotel Booking Lite plugin version 5.2.3 or lower is installed AND the plugin contains vulnerable dynamic code inclusion patterns accessible without authentication.
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 a patched version of Hotel Booking Lite (version > 5.2.3) immediately. If no patch is available, disable the plugin or restrict access to the affected endpoints via web server configuration until a fix is released.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-66078 — 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-2025-66078 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