PatchTheCVECVE-2022-4443: The BruteBank WordPress plugin before 1.9 does not have CSRF check in place when updating its settings, which
CVE-2022-4443 is a medium-severity flaw (CVSS 6.5) affecting brutebank. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
The BruteBank WordPress plugin before 1.9 does not have CSRF check in place when updating its settings, which could allow attackers to make a logged-in admin change them via a CSRF attack.
Why this priority
- Public exploit reference
A fixed release or distro patch exists.
Risk facts
| CVSS score | 6.5 (Medium) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | Required |
| EPSS exploit chance | 0.3% (top 74%) |
| CISA exploited list | No |
| Published | 2023-01-23 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2022-4443?
brutebank: upgrade to 1.9. Exact commands for each OS are on this page.
Is CVE-2022-4443 being exploited?
CVE-2022-4443 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2022-4443 affect?
CVE-2022-4443 affects brutebank. Severity is medium (CVSS 6.5). The BruteBank WordPress plugin before 1.9 does not have CSRF check in place when updating its settings, which could allow attackers to make a logged-in admin change them via a CSRF attack.
How urgent is CVE-2022-4443?
Priority 34/100. Public exploit reference