WPBruiser Security – No CAPTCHA Anti-Spam & Login Protection <= 3.6.2 - Authenticated (Subscriber+) Brute-Force Lockout Bypass
Strategic Overview
- Status
- Patched in 3.6.3
- Affected Plugin
- WPBruiser Security – No CAPTCHA Anti-Spam & Login Protection
- Affected Version
<= 3.6.2- CVSS
- 4.3Medium
- Weakness type
- CWE-287 · Improper Authentication
- CVE
CVE-2026-121612
At a glance
CVE-2026-121612 is a medium-severity Improper Authentication vulnerability in the WPBruiser Security WordPress plugin, affecting versions <= 3.6.2. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 3.6.3; sites on affected versions should update now. Disclosed November 2026, reported by Aarush Gaur.
Vulnerability Overview
The WPBruiser Security – No CAPTCHA Anti-Spam & Login Protection plugin for WordPress is vulnerable to account lockout bypass in all versions up to, and including, 3.6.2. This makes it possible for authenticated attackers, with Subscriber-level access and above, to bypass account lockouts when they have been blocked from brute force.
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.
CWE-287: Improper Authentication
Reaching this weakness in WPBruiser Security <= 3.6.2 takes an account at Subscriber level or above. Improper authentication means the mechanism that proves who a caller is can be satisfied without the secret it was supposed to require.
An attacker authenticates as another user — administrators included — without ever knowing a password, so password policies and login rate limits never come into play. For WPBruiser Security the fix is 3.6.3: builds <= 3.6.2 are affected, anything from 3.6.3 onward is not.
Remediation
Update to version 3.6.3, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: WPBruiser Security 3.6.3 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in WPBruiser Security – No CAPTCHA Anti-Spam & Login Protection
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C