dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2026-25413

CRITICAL · 9.9 CVSS v3.1 Published 2026-03-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
Unrestricted Upload of File with Dangerous Type vulnerability in iqonicdesign WPBookit Pro wpbookit-pro allows Using Malicious Files.This issue affects WPBookit Pro: from n/a through <= 1.6.18.

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 confidence

The WPBookit Pro WordPress plugin before version 1.6.19 contains an unrestricted file upload vulnerability that allows authenticated attackers to upload malicious files (e.g., PHP shells, executable scripts) without proper validation of file types or content. This can lead to remote code execution on the WordPress server.

MitigationUpdate WPBookit Pro to version 1.6.19 or later once released. Until a patch is available, disable the plugin or restrict file upload functionality through web server configuration (e.g., .htaccess rules to block script execution 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
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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. Locate WPBookit Pro plugin installation
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'wpbookit', 'wpbookit-pro', or similar. Alternatively, log into WordPress admin and navigate to Plugins > Installed Plugins to find the plugin.
    Affected if The plugin folder exists in the plugins directory or the plugin appears in the WordPress admin plugins list.
  2. Determine installed plugin version
    Open the main plugin file (usually wpbookit.php or wpbookit-pro.php in the plugin folder) and look for a version comment or constant at the top of the file. Or check the plugin version displayed in WordPress admin under Plugins > Installed Plugins.
    Affected if The version number found is lower than 1.6.19, or no version is displayed (indicating an older installation).
  3. Verify plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and check if WPBookit Pro is activated. Or query the WordPress database options table for the option_name containing 'active_plugins'.
    Affected if The plugin shows as 'Active' in the admin or 'active_plugins' option includes the plugin.
  4. Confirm file upload capability is accessible
    Identify if the booking or appointment functionality that includes file uploads is publicly accessible or available to user roles below administrator. Check plugin settings under WPBookit Pro settings page for any file upload options and their visibility/permissions.
    Affected if File upload forms (such as for document attachments, profile images, or booking-related files) are enabled and accessible to authenticated users (subscriber, customer, or similar roles).
  5. Inspect upload directories for suspicious files
    Check the WordPress uploads folder (typically wp-content/uploads/) and any custom upload directories configured in WPBookit Pro settings. Look for unexpected file extensions such as .php, .phtml, .phar, .exe, or .js that could indicate malicious uploads.
    Affected if Executable or script files (.php, .phtml, etc.) are found in upload directories, especially if they were uploaded recently or contain obfuscated code.

Your environment is affected if WPBookit Pro is installed, active, and running a version lower than 1.6.19 with file upload functionality accessible to authenticated users.

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

Update WPBookit Pro to version 1.6.19 or later once released. Until a patch is available, disable the plugin or restrict file upload functionality through web server configuration (e.g., .htaccess rules to block script execution in upload directories).

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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