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

CVE-2025-27011

HIGH · 7.5 CVSS v3.1 Published 2025-04-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Remotely reachable 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 magepeopleteam Booking and Rental Manager booking-and-rental-manager-for-woocommerce allows PHP Local File Inclusion.This issue affects Booking and Rental Manager: from n/a through <= 2.2.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

This is a PHP Local File Inclusion (LFI) vulnerability in the magepeopleteam Booking and Rental Manager plugin for WooCommerce. The plugin fails to properly validate or sanitize user-controlled input used in PHP include/require statements, allowing attackers to include and execute arbitrary local PHP files on the server.

MitigationUpdate to the latest version of the plugin when available; prior to patch, implement web application firewall rules to block suspicious include path parameters and audit the codebase for vulnerable include/require statements.

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 checks

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

  1. Confirm plugin is installed
    Log in to WordPress admin and navigate to Plugins > Installed Plugins. Look for 'Booking and Rental Manager for WooCommerce' or 'magepeopleteam' in the plugin list.
    Affected if The plugin is present in the WordPress installation
  2. Identify the installed plugin version
    In the WordPress Plugins page, click on the plugin name to view details, or check the plugin header comment in the main PHP file (typically in /wp-content/plugins/magebooking-plugin-file/...)
    Affected if The version displayed is older than the patched version (compare against vendor release notes for the fix)
  3. Locate the plugin's main include files
    Examine the plugin directory structure. Look for PHP files containing include(), require(), include_once(), or require_once() statements that use variables or request parameters for the file path.
    Affected if The plugin code contains include/require statements using unsanitized user input (e.g., $_GET, $_POST, or directly parsed parameters)
  4. Search for vulnerable parameter handling
    Search the plugin source code for patterns where request parameters (like 'file', 'path', 'page', 'template', or similar) are used in include/require statements without proper validation using functions like basename(), realpath(), or allowlist checks.
    Affected if Parameters from HTTP requests are used directly in file inclusion functions without sanitization
  5. Check web server access logs for exploitation attempts
    Review web server access logs (Apache/nginx) for requests to the plugin's PHP files with suspicious query parameters such as ?file=../../, ?path=..., or similar patterns that attempt directory traversal.
    Affected if Logs show incoming requests with traversal sequences or suspicious file inclusion parameters targeting the plugin

You are affected if the magepeopleteam Booking and Rental Manager plugin is installed and its version predates the patched release, particularly if the codebase contains include/require statements using unsanitized user-supplied input.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to the latest version of the plugin when available; prior to patch, implement web application firewall rules to block suspicious include path parameters and audit the codebase for vulnerable include/require statements.

Recommended fix Moderate confidence

Latest version of Booking and Rental Manager for WooCommerce (version 2.2.9 or newer)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'Booking and Rental Manager for WooCommerce' plugin by magepeopleteam
  4. Check if an update is available and install the latest version
  5. Verify the updated version is at least 2.2.9 or higher

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-27011 — 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-27011 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