CVE-2025-27264
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 Creativeitem Doctor Appointment Booking doctor-appointment-booking allows PHP Local File Inclusion.This issue affects Doctor Appointment Booking: from n/a through <= 1.0.0.
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 confidenceThis is a PHP Local File Inclusion (LFI) vulnerability in the Creativeitem Doctor Appointment Booking plugin that allows attackers to read sensitive local files on the server due to improper control of filenames in include/require statements. The vulnerability stems from unsanitized user input being used in PHP file inclusion functions, enabling path traversal attacks.
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.
-
Confirm plugin installationLocate the Creativeitem Doctor Appointment Booking plugin in your PHP application (typically in wp-content/plugins/ or similar plugin directory). Use your package manager, file system search, or CMS plugin list to verify presence.Affected if The plugin is installed and active in the application.
-
Identify plugin versionCheck the plugin's main PHP file for a version constant or header comment, or look for a version.xml/readme.txt file within the plugin directory. Compare against any published version information.Affected if The installed version is unknown or older than the patched version.
-
Locate file inclusion codeSearch the plugin source code for include, require, include_once, or require_once statements that use variables (such as $_GET, $_POST, or unvalidated parameters) without proper sanitization. Look for patterns like 'include($_GET["page"])' or similar dynamic file inclusion.Affected if Dynamic file inclusion using unsanitized user input exists in the plugin code.
-
Test for path traversal exposureIf dynamic inclusion is found, attempt a controlled test (or review access logs) using a path traversal payload such as '../../../../etc/passwd' in the vulnerable parameter to see if file contents are returned.Affected if The application returns contents of files outside the intended directory.
You are affected if the Creativeitem Doctor Appointment Booking plugin is installed with dynamic file inclusion code that allows unsanitized user input to control which files are included, enabling path traversal attacks.
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 using whitelist-based file inclusion, sanitize paths with basename() and realpath(), and ensure included files are restricted to expected directories to prevent unauthorized file access.
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-27264 — 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-27264 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