CVE-2025-53259
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.7.
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 · high confidenceLocal File Inclusion (LFI) vulnerability in nicdark Hotel Booking nd-booking allows attackers to include arbitrary local PHP files via insecure use of include/require statements. This can lead to remote code execution if the attacker can upload malicious files or access sensitive system 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 component is installedSearch your codebase for files containing 'nd-booking', 'nicdark', or the booking system module directoriesAffected if The nd-booking component is present in your environment
-
Identify the nd-booking versionCheck composer.json, plugin metadata, or version file within the nd-booking module directory for version informationAffected if The installed version falls within any vulnerable range or cannot be determined (treat as potentially affected)
-
Locate include/require statements handling file pathsSearch PHP files in the nd-booking module for patterns like 'include', 'require', 'include_once', 'require_once' with variables in the path argument (e.g., include($file), require($_GET['page'])Affected if Dynamic file inclusion using user-supplied input is found in nd-booking PHP files
-
Inspect the vulnerable parameter sourceIf dynamic inclusion is found, examine which superglobal (GET, POST, COOKIE, REQUEST) or input source feeds the include/require pathAffected if User input directly or indirectly controls the file path in include/require statements without validation
-
Check file upload or write accessVerify if any file upload functionality exists in nd-booking or if the web server user has write access to writable directories that could contain malicious PHP filesAffected if An attacker could upload or place malicious PHP files for inclusion
Your environment is affected if nd-booking is installed and contains dynamic include/require statements using user-controlled input without validation or whitelist filtering.
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 file path parameters, use whitelisting for allowed files, or replace dynamic file inclusion with a switch/case structure. Additionally, disable allow_url_include and ensure proper file permission restrictions.
- 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-53259 — 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-53259 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