CVE-2026-32384
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 magepeopleteam WpBookingly service-booking-manager allows PHP Local File Inclusion.This issue affects WpBookingly: from n/a through <= 1.2.9.
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 WpBookingly WordPress plugin by magepeopleteam. The plugin's include/require statements improperly validate user-controlled input for file paths, allowing attackers to potentially read sensitive local files or achieve remote code execution by including malicious PHP 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 WpBookingly plugin is installedCheck the WordPress plugins directory (wp-content/plugins/) for a folder named 'wpbookingly', 'WpBookingly', or 'magepeopleteam-booking' and list its contents.Affected if The plugin folder exists in the WordPress plugins directory.
-
Determine installed plugin versionOpen the plugin's main PHP file (typically wp-content/plugins/[plugin-folder]/wpbookingly.php or similar) and locate the version comment/header, or check the readme.txt file for the 'Stable tag' version number.Affected if The installed version is lower than the patched version released for CVE-2026-32384.
-
Identify vulnerable include/require codeSearch within the plugin directory for PHP include(), require(), include_once(), or require_once() statements that use variables or user input, such as: include($_GET['file']), include($path . $_REQUEST['template']), or similar patterns.Affected if The plugin contains dynamic file inclusion using unsanitized user input (GET, POST, or REQUEST parameters).
-
Test if file inclusion is accessible via web requestIf Step 3 identifies vulnerable code, attempt a benign test request to the affected endpoint with a controlled parameter (e.g., ?file=../../../../wp-config.php) to confirm the LFI is exploitable from HTTP requests.Affected if The vulnerable file inclusion endpoint responds with file contents from outside the intended directory.
You are affected if the WpBookingly plugin is installed, contains dynamic file inclusion using unsanitized user input, and that endpoint is accessible via HTTP requests allowing path traversal.
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 dataUpdate WpBookingly to the latest patched version immediately. If no patched version is available, disable the plugin and review server configurations to restrict PHP file operations and disable allow_url_include.
- Consultation3.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-32384 — 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-2026-32384 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