CVE-2025-32155
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 markkinchin Beds24 Online Booking beds24-online-booking allows PHP Local File Inclusion.This issue affects Beds24 Online Booking: from n/a through <= 2.0.28.
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 confidenceThe Beds24 Online Booking WordPress plugin (versions <= 2.0.28) contains a PHP Local File Inclusion (LFI) vulnerability where user-supplied input is not properly validated before being used in include/require statements, allowing authenticated attackers to read sensitive files from the server filesystem.
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 Beds24 Online Booking plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Beds24 Online Booking', or check the plugin files in /wp-content/plugins/beds24-online-booking/ for a version fileAffected if The plugin is present in the WordPress installation
-
Determine the installed plugin versionCheck the plugin main file (e.g., beds24-online-booking.php) for the 'Version' header comment, or look in the plugin's readme.txt fileAffected if The version is 2.0.28 or lower
-
Locate file inclusion code pathsSearch the plugin directory for PHP files containing include, require, include_once, or require_once statements that use variables from $_GET, $_POST, or $_REQUEST without sanitization - grep for patterns like 'include($_REQUEST' or 'require($' within the plugin folderAffected if User-controllable input is used directly in file inclusion functions without validation
-
Identify the vulnerable parameterExamine identified inclusion code for the specific parameter name (commonly something like 'page', 'file', 'template', or 'path' in the request) that gets passed to include/requireAffected if A parameter allows path traversal (e.g., ../../) to reach files outside the intended directory
-
Confirm authentication requirementVerify the plugin requires user authentication (even low-privilege users) to trigger the file inclusion - check if the vulnerable code is accessible only to logged-in usersAffected if The attacker needs any valid WordPress user credentials to exploit this flaw
You are affected if the Beds24 Online Booking plugin version is 2.0.28 or lower AND your WordPress site has users (even subscribers) who could trigger the vulnerable file inclusion parameter.
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 a patched version of Beds24 Online Booking. If no patched version is available, implement strict input validation and use allowlists for any file inclusion logic, avoiding direct use of user input in include/require statements.
- 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-32155 — 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-32155 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