CVE-2025-12685

WPBookit <= 1.0.7 - Cross-Site Request Forgery to Customer Deletion

2025-12-12 00:00
Drtime

Strategic Overview

Status
Unpatched
Affected Plugin
WPBookit
Affected Version
<= 1.0.7
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2025-12685
View all WPBookit vulnerabilities

At a glance

CVE-2025-12685 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the WPBookit WordPress plugin, affecting versions <= 1.0.7. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed December 2025, reported by Drtime.

Vulnerability Overview

The WPBookit plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.0.7. This is due to missing or incorrect nonce validation on the 'delete_customer' route. This makes it possible for unauthenticated attackers to delete customers via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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 privileges on the target site.

CWE-352: Cross-Site Request Forgery (CSRF)

WPBookit <= 1.0.7 carries this weakness at delete_customer, and reaching it takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. No fixed build of this plugin is recorded for WPBookit yet, so installs running <= 1.0.7 stay exposed until the vendor ships one.

Remediation

No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.

How does WordSec protect against this?

The attempt arrives as an ordinary request to WPBookit: WordSec's web application firewall inspects request payloads before WordPress loads them. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-12685https://www.wordfence.com/threat-intel/vulnerabilities/id/1da1d851-10ba-45e8-a486-03ac409075a4https://nvd.nist.gov/vuln/detail/CVE-2025-12685

Related records

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