WPBase Cache <= 5.5.6 - Authenticated (Subscriber+) Denial of Service
Strategic Overview
- Status
- Unpatched
- Affected Plugin
- WPBase Cache
- Affected Version
<= 5.5.6- CVSS
- 6.5Medium
- Weakness type
- CWE-400 · Uncontrolled Resource Consumption
- CVE
CVE-2026-39767
At a glance
CVE-2026-39767 is a medium-severity Uncontrolled Resource Consumption vulnerability in the WPBase Cache WordPress plugin, affecting versions <= 5.5.6. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high availability impact). Exploitation requires an authenticated account at Subscriber level or above. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed October 2026, reported by dodoh4t.
Vulnerability Overview
The WPBase Cache plugin for WordPress is vulnerable to Denial of Service in all versions up to, and including, 5.5.6. This is due to insufficient validation of user supplied input. This makes it possible for authenticated attackers, with subscriber-level access and above, to make the affected site unavailable.
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 availability.
CWE-400: Uncontrolled Resource Consumption
Reaching this weakness in WPBase Cache <= 5.5.6 takes an account at Subscriber level or above. Uncontrolled resource consumption means a request can make the server do an amount of work it never bounds, because the size or repetition of the job is taken from the request rather than capped by the code.
A single caller can hold PHP workers, database connections or disk open long enough to slow the site for everyone, without needing any account or any other flaw. No fixed build of this plugin is recorded for WPBase Cache yet, so installs running <= 5.5.6 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?
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. 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
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C