Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as low-privilege user
-
DeliveryAccess file upload functionality
-
ExploitUpload malicious file with dangerous type
-
ExecutionExecute arbitrary code on server
-
ImpactCompromise site and data
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V5 - File Handling File type validation, storage isolation
MITRE ATT&CK
2 techniques across 2 tactics: Command and Control, Persistence The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Authenticated user with low-privilege access to WordPress site running WPBookit Pro plugin version ≤1.6.18. Attacker uploads malicious file through plugin's upload functionality without victim interaction required. |
| Impact | This vulnerability presents a critical real-world risk despite the absence of a CVSS score and EPSS data in the provided intelligence. The attack vector is network-based with no authentication required, making it highly accessible to unauthenticated threat actors. CWE-434 vulnerabilities are consistently exploitable and have a clear technical impact (remote code execution). The vulnerability affects an active WordPress plugin with a defined affected version range (up to 1.6.18), and the Patchstack reporting suggests this is a known, documented issue. Given that file upload vulnerabilities are frequently the target of automated scanners and mass exploitation campaigns, this should be treated as a high-priority vulnerability regardless of missing CVSS metrics. The fact that Patchstack has catalogued it with a specific EUVD ID (EUVD-2026-15720) further validates its legitimacy and exploitation likelihood. |
| Exploit ScenarioDerived | An unauthenticated attacker discovers a WPBookit Pro installation running version 1.6.18 or earlier through WordPress plugin enumeration or Shodan/similar scanning. The attacker crafts a malicious PHP webshell, bypasses the plugin's insufficient file type validation by uploading it with a spoofed extension or by exploiting a null-byte injection, and accesses the uploaded file via direct HTTP request to execute arbitrary code. Within minutes, the attacker gains persistent web shell access, enumerates database credentials from wp-config.php, exfiltrates customer booking data, or deploys ransomware across the compromised WordPress installation and associated server infrastructure. No special privileges or interaction are required from the site administrator. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Mar 25, 2026
WPBookit Pro through version 1.6.18 contains an unrestricted file upload vulnerability (CWE-434) that allows attackers to upload malicious files to affected WordPress installations. This arbitrary file upload flaw enables remote code execution and complete site compromise without requiring authentication or special privileges. The vulnerability affects all versions of the iqonicdesign WPBookit Pro plugin up to and including 1.6.18, making it a critical risk for WordPress administrators using this booking plugin.
RemediationAI
The primary remediation is to upgrade WPBookit Pro to the patched version immediately (check the plugin vendor website or WordPress plugin repository for the latest version beyond 1.6.18). Until patching is completed, WordPress administrators should disable the WPBookit Pro plugin entirely or restrict access to its upload functionality via web application firewall (WAF) rules or .htaccess restrictions blocking file uploads to plugin directories. Additionally, implement the principle of least privilege by ensuring the web server process runs with minimal permissions, disable PHP execution in upload directories via web server configuration (e.g., Apache or Nginx directives), and enable comprehensive file integrity monitoring and access logging on the WordPress installation. Monitor for suspicious file uploads and unexpected PHP files in the wp-content/plugins/wpbookit-pro/ directory. For detailed patching instructions, consult the Patchstack advisory at https://patchstack.com/database/Wordpress/Plugin/wpbookit-pro/vulnerability/wordpress-wpbookit-pro-plugin-1-6-18-arbitrary-file-upload-vulnerability.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability exists in the WPBookit Pro WordPress plugin (CPE: cpe:2.3:a:iqonicdesign:wpbookit_pro:*:*:*:*:*:*:*:*), which is a booking/appointment scheduling solution for WordPress. The root cause is classified under CWE-434 (Unrestricted Upload of File with Dangerous Type), indicating that the plugin's file upload functionality lacks proper validation and filtering of uploaded file types. This allows attackers to bypass file type restrictions and upload executable files (such as PHP files) to the web server. Once uploaded, these malicious files can be executed by the web server, leading to arbitrary code execution within the context of the WordPress application and underlying operating system.
Know when Wpbookit Pro gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
DescriptionCVE.org
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.
Executive ViewAI
CVE-2026-25413 presents critical security risk, a unrestricted file upload vulnerability rated CVSS 9.9. This could allow attackers to access or modify files outside intended directories, potentially exposing sensitive configuration or credentials. Organizations should apply vendor updates immediately when available and implement compensating controls in the interim.
Apply vendor patch. If immediate patching is not feasible: (1) Restrict file upload functionality via WAF; (2) Implement allowlist-based file type validation; (3) Use chroot/containerization to limit filesystem access.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Malicious file upload attacks exploit insufficient validation when web applications accept user-provided files.
EUVD-2026-15720
NVD
CVE.org
EPSS
Vulnrichment
VulDB
GitHub PoC
Exploit-DB