CVE-2025-6057

WPBookit <= 1.0.4 - Authenticated (Subscriber+) Arbitrary File Upload

2025-07-11 00:00
theviper17y

Strategic Overview

Status
Patched in 1.0.5
Affected Plugin
WPBookit
Affected Version
<= 1.0.4
CVSS
8.8High
Weakness type
CWE-434 · Unrestricted Upload of File with Dangerous Type
CVE
CVE-2025-6057
View all WPBookit vulnerabilities

At a glance

CVE-2025-6057 is a high-severity Unrestricted Upload of File with Dangerous Type vulnerability in the WPBookit WordPress plugin, affecting versions <= 1.0.4. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 1.0.5; sites on affected versions should update now. Disclosed July 2025, reported by theviper17y.

Vulnerability Overview

The WPBookit plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the handle_image_upload() function in all versions up to, and including, 1.0.4. This makes it possible for authenticated attackers, with Subscriber-level access and above, to upload arbitrary files on the affected site's server which may make remote code execution possible.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-434: Unrestricted Upload of File with Dangerous Type

WPBookit <= 1.0.4 carries this weakness at handle_image_upload(), and reaching it takes an account at Subscriber level or above. An unrestricted file upload lets a caller store a file whose type or destination the application does not properly constrain.

If an uploaded file lands anywhere the server will execute, the flaw becomes remote code execution and the site should be treated as fully compromised. For WPBookit the fix is 1.0.5: builds <= 1.0.4 are affected, anything from 1.0.5 onward is not.

Remediation

Update to version 1.0.5, or a newer patched version

How does WordSec protect against this?

An attacker needs Subscriber access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: WPBookit 1.0.5 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Scanner
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-6057https://www.wordfence.com/threat-intel/vulnerabilities/id/fac81cc0-c6c9-4009-aacb-52adc70c0261https://nvd.nist.gov/vuln/detail/CVE-2025-6057

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C