WordPress Brute Force Protection – Stop Brute Force Attacks
guardgiant · plugin
Known security vulnerabilities for WordPress Brute Force Protection – Stop Brute Force Attacks. Find out in seconds which version runs on your site with WP Lens.
2 known vulnerabilities
1 exploitable without logging in · latest Nov 23, 2024
Closed on wordpress.org
Removed from the directory on Nov 21, 2024 · reason: security issue. A closed component gets no more updates; installed copies keep running and their vulnerabilities stay open. Remove it or replace it with a maintained alternative.
wordpress.org status checked on Oct 2, 2026
Vulnerabilities
- High 7.2
CVE-2023-48764high privilege≤ 2.2.5
WordPress WordPress Brute Force Protection – Stop Brute Force Attacks Plugin <= 2.2.5 is vulnerable to SQL Injection
- Medium 6.1
CVE-2024-10869unauthenticated · needs a click≤ 2.2.6
GuardGiant Brute Force Protection <= 2.2.6 - Reflected Cross-Site Scripting
The access label is read from the record's own text (e.g. “subscriber+”: subscriber and above). When the text names no role, CVSS decides between “login required” and “high privilege”; no role name is invented. “Needs a click”: the attack depends on a logged-in user following a link (CSRF, reflected XSS).