WordPress plugin
WordPress Brute Force Protection – Stop Brute Force Attacks security & vulnerabilities
Unpatched vulnerability in the latest version
At least one vulnerability affects the latest version and no fix has been released. Deactivate the plugin or restrict access to the affected feature until the vendor ships a patch.
- Critical0
- High0
- Medium2
- Low0
All WordPress Brute Force Protection – Stop Brute Force Attacks vulnerabilities
| Severity | Vulnerability | CVE | Published |
|---|---|---|---|
| Medium6.1 | Reflected Cross-Site Scripting ≤2.2.6No patch available | CVE-2024-10869 | |
| Medium6.6 | Authenticated (Administrator+) SQL Injection via orderby ≤2.2.5Update to 2.2.6 | CVE-2023-48764 |
- Medium6.1Reflected Cross-Site Scripting
≤2.2.6No patch available
- Medium6.6Authenticated (Administrator+) SQL Injection via orderby
≤2.2.5Update to 2.2.6
WordPress Brute Force Protection – Stop Brute Force Attacks: common questions
Does WordPress Brute Force Protection – Stop Brute Force Attacks have known vulnerabilities?
Yes. VulnCrest Radar lists 2 known vulnerabilities in WordPress Brute Force Protection – Stop Brute Force Attacks: 2 medium. At least one is not fixed in the latest version.
How do I check which version of WordPress Brute Force Protection – Stop Brute Force Attacks I run?
In wp-admin open Plugins → Installed Plugins; the version is shown under the name. Without admin access, our passive Check my site tool can often read it from public files.
What is the most recent WordPress Brute Force Protection – Stop Brute Force Attacks vulnerability?
CVE-2024-10869, published Nov 22, 2024: GuardGiant Brute Force Protection <= 2.2.6 - Reflected Cross-Site Scripting. Severity: Medium (CVSS 6.1).
Is any WordPress Brute Force Protection – Stop Brute Force Attacks vulnerability listed in CISA KEV?
No. None of the known WordPress Brute Force Protection – Stop Brute Force Attacks vulnerabilities is currently listed in the CISA KEV catalog.