# Loginizer <= 2.1.3 - Unauthenticated Brute Force Protection Bypass via Special Characters in Request URL

- **ID:** WPSEC-2026-3534
- **Plugin:** Loginizer (`loginizer`), https://wordpress.org/plugins/loginizer/
- **Affected versions:** from 1.3.9 before 2.1.4
- **Fixed in:** 2.1.4 (Update to 2.1.4 or later.)
- **Severity:** Medium 5.3 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N)
- **Weakness:** CWE-307
- **Usage among sites WPSec scans:** plugin Low, affected versions Low (as of 2026-11-20)
- **Attack surface analysis:** https://attacksurface.wpsec.com/plugin/loginizer
- **Fix released:** 2026-11-19
- **Published:** 2026-11-20
- **URL:** https://wpsec.com/vuln/WPSEC-2026-3534/

## Description

The Loginizer plugin for WordPress is vulnerable to a brute force protection bypass via special characters in the login request URL in all versions up to, and including, 2.1.3, due to the plugin storing the raw request URL in its failed-login log without removing bytes the database cannot store (such as invalid UTF-8). WordPress refuses the whole query when it contains such bytes, so the failed attempt is never recorded and the lockout counter never increases. This makes it possible for unauthenticated attackers to make unlimited password guesses against wp-login.php or xmlrpc.php without triggering the lockout.

## References

- https://wpsec.com/vuln/WPSEC-2026-3534/
- https://plugins.svn.wordpress.org/loginizer/tags/2.1.4/
- https://wordpress.org/plugins/loginizer/

Source: WPSec, https://wpsec.com/vuln/WPSEC-2026-3534/

License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Free to use, share and adapt, also commercially, if you credit WPSec and link to this advisory.
