Anti-Malware Security and Brute-Force Firewall <= 4.15.22 - Cross-Site Request Forgery
Strategic Overview
- Status
- Patched in 4.15.23
- Affected Plugin
- Anti-Malware Security and Brute-Force Firewall
- Affected Version
< 4.15.23- CVSS
- 3.1Low
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE pending
At a glance
This record tracks a low-severity Cross-Site Request Forgery (CSRF) vulnerability in the Anti-Malware Security and Brute-Force Firewall WordPress plugin, affecting versions < 4.15.23. It carries a CVSS score of 3.1 (reachable over the network). Exploitation requires no authentication. The issue is fixed in version 4.15.23; sites on affected versions should update now. Disclosed May 2015, reported by James Hooker.
Vulnerability Overview
The Anti-Malware Security and Brute-Force Firewall plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 4.15.22. This makes it possible for unauthenticated attackers to consume resource utilization (by performing a large number of scans simultaneously), via forged request granted they can trick a site administrator into performing an action such as clicking on a link.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, and no privileges on the target site.
CWE-352: Cross-Site Request Forgery (CSRF)
Reaching this weakness in Anti-Malware Security and Brute-Force Firewall < 4.15.23 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.
An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Anti-Malware Security and Brute-Force Firewall the fix is 4.15.23: builds < 4.15.23 are affected, anything from 4.15.23 onward is not.
Remediation
Update to version 4.15.23, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Anti-Malware Security and Brute-Force Firewall: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Anti-Malware Security and Brute-Force Firewall 4.15.23 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in Anti-Malware Security and Brute-Force Firewall
- 9.0CVE-2024-22144: Anti-Malware Security and Brute-Force Firewall RCE
CVE-2024-22144 - 7.5CVE-2026-39478: Anti-Malware Security… PHP Object Injection
CVE-2026-39478 - 7.2CVE-2026-57691: Anti-Malware Security and Brute-Force… Stored XSS
CVE-2026-57691 - 7.2CVE-2022-4327: Anti-Malware Security… PHP Object Injection
CVE-2022-4327 - 7.2Anti-Malware Security and Brute-Force Firewall <= 4.15.17 XSS
- 6.5CVE-2025-11705: Anti-Malware Security… Authenticated (Subscriber+)
CVE-2025-11705 - 6.1CVE-2022-0953: Anti-Malware Security and Brute-Force… Reflected XSS
CVE-2022-0953 - 6.1CVE-2022-2599: Anti-Malware Security and Brute-Force… Reflected XSS
CVE-2022-2599
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C