dbcve.org
PHP File Inclusion (RFI/LFI)Weakness · CWE-98

CVE-2025-64287

HIGH · 8.1 CVSS v3.1 Published 2025-11-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in Edge-Themes Alloggio - Hotel Booking alloggio allows PHP Local File Inclusion.This issue affects Alloggio - Hotel Booking: from n/a through <= 1.8.

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 confidence

The Alloggio - Hotel Booking theme <= 1.8 contains a PHP Local File Inclusion (LFI) vulnerability due to improper control of filenames in include/require statements. Attackers can potentially include arbitrary local PHP files by manipulating input parameters, leading to code execution.

MitigationUpgrade to a patched version of Alloggio - Hotel Booking. If no patch available, implement strict input validation on all file inclusion parameters and ensure PHP execution is disabled in upload directories.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Alloggio theme is installed
    Check the wp-content/themes directory for the alloggio theme folder, or list installed themes via WordPress admin under Appearance > Themes
    Affected if The alloggio theme folder exists in the WordPress themes directory
  2. Identify the installed theme version
    Open the style.css file in wp-content/themes/alloggio and read the 'Version:' header in the file comments, or check theme.json for version metadata
    Affected if The installed version matches or precedes the version that fixed this LFI vulnerability (compare against the vendor's security advisory)
  3. Locate vulnerable include/require statements
    Search PHP files in the alloggio theme directory for patterns like 'include($_GET' or 'require($_POST' or similar unsanitized parameter usage in include/require/require_once/include_once statements
    Affected if Unsanitized user-controlled parameters are used directly in include or require statements within theme PHP files
  4. Check for the specific vulnerable parameter
    Inspect the identified include/require calls to see which GET/POST parameters control the file path (common parameter names may include 'page', 'file', 'path', 'template', or 'include')
    Affected if A parameter passed through URL or form input directly injects file paths into include/require without validation or filtering
  5. Confirm the vulnerable code path is reachable
    Attempt to access the affected page/feature that uses the vulnerable include statement (e.g., by visiting a URL like ?page=../../../../etc/passdd or similar path traversal attempts), ensuring the feature is enabled
    Affected if The code path containing the vulnerable include/require is accessible without authentication or is accessible to authenticated users and the parameter is accepted
  6. Review PHP configuration for mitigations
    Check php.ini for allow_url_fopen=Off and allow_url_include=Off settings; also verify that open_basedir restrictions are in place if possible
    Affected if These PHP configuration mitigations are disabled or not set, leaving the server more exposed to LFI exploitation

You are affected if the Alloggio theme is installed and uses an unsanitized parameter in include/require statements that can be manipulated via HTTP requests to include arbitrary local PHP files.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a patched version of Alloggio - Hotel Booking. If no patch available, implement strict input validation on all file inclusion parameters and ensure PHP execution is disabled in upload directories.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-64287 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-64287 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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