CVE-2025-47498
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 Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in nicdark Hotel Booking nd-booking allows PHP Local File Inclusion.This issue affects Hotel Booking: from n/a through <= 3.6.
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 nicdark Hotel Booking nd-booking plugin for WordPress contains a PHP Local File Inclusion (LFI) vulnerability where user-supplied input is improperly validated before being used in include/require statements. An unauthenticated attacker could exploit this to include arbitrary PHP files from the local filesystem, potentially leading to remote code execution if they can upload files or access sensitive configuration files.
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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/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 nd-booking plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'nicdark Hotel Booking' or 'nd-booking'. Alternatively, check the filesystem at /wp-content/plugins/ for a directory named 'nd-booking' or similar.Affected if The nd-booking plugin is present in the WordPress installation
-
Identify installed plugin versionCheck the plugin's main PHP file header for the Version comment, or look for a readme.txt file in the plugin directory which typically contains version metadata.Affected if The installed version matches any affected version range (compare your version to known affected releases)
-
Locate file inclusion code in the pluginSearch plugin PHP files for patterns like 'include(', 'require(', 'include_once(', 'require_once(' where a variable is passed directly, such as 'include $_GET["file"]' or 'require $file'. Use grep or IDE search across the nd-booking plugin directory.Affected if Dynamic file inclusion using unsanitized user input is found in the plugin code
-
Check for exposed file path parametersReview the plugin's PHP files that handle HTTP request parameters (GET/POST) and identify if any parameter is used in include/require statements without validation, particularly looking for parameters that accept file paths.Affected if User-supplied parameters from requests are used in file inclusion without validation
If the nd-booking plugin is installed and contains dynamic file inclusion code using unsanitized user input, the environment is affected by CVE-2025-47498.
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 dataImplement strict input validation on all file path parameters used in include/require statements, preferably using a whitelist approach, or refactor to avoid dynamic file inclusion entirely.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47498 — 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-47498 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