CVE-2025-39526
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 confidenceLocal File Inclusion vulnerability in the nicdark Hotel Booking nd-booking plugin allows attackers to include arbitrary local files via improper input validation in PHP include/require statements. This LFI flaw could enable sensitive data disclosure or potentially lead to 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/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.
-
Confirm nd-booking plugin is installedLog into WordPress admin and navigate to Plugins > Installed Plugins. Look for 'nicdark Hotel Booking' or 'nd-booking' in the list of active plugins.Affected if The plugin is present and active in the WordPress installation
-
Identify the installed versionIn WordPress admin, click on the nd-booking plugin to view its details, or check the plugin header in /wp-content/plugins/nd-booking/ directory for the Version field.Affected if The installed version is older than the patched version (the specific version numbers were not disclosed in the CVE)
-
Check for vulnerable file inclusion patternsExamine PHP files in the nd-booking plugin directory, specifically looking for include(), require(), include_once(), or require_once() statements that use variables or user input without proper sanitization.Affected if The plugin contains include/require statements using unsanitized user input
-
Identify the vulnerable parameterReview plugin files that handle HTTP request parameters (GET/POST) and trace whether those parameters flow into include or require statements without validation.Affected if User-supplied parameters can be directly used in file inclusion functions without validation
-
Inspect PHP configuration for additional riskCheck php.ini or phpinfo() for the allow_url_include setting. While this CVE is LFI (local), having allow_url_include enabled would increase overall risk.Affected if allow_url_include is enabled (this is a secondary risk indicator for file inclusion vulnerabilities)
A defender is affected if the nd-booking plugin is installed, the installed version predates the patch, and the plugin contains file inclusion code that processes user input without validation.
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 version of nd-booking; implement strict input validation and whitelist-based file inclusion controls; disable allow_url_include in PHP configuration.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-39526 — 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-39526 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