All In One WP Security <= 5.2.6 - Cross-Site Request Forgery to IP Blocking
Strategic Overview
- Status
- Patched in 5.2.7
- Affected Plugin
- All-In-One Security (AIOS) – Security and Firewall
- Affected Version
<= 5.2.6- CVSS
- 4.3Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2024-30468
At a glance
CVE-2024-30468 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the All-In-One Security (AIOS) WordPress plugin, affecting versions <= 5.2.6. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 5.2.7; sites on affected versions should update now. Disclosed February 2024, reported by Ananda Dhakal.
Vulnerability Overview
The All-In-One Security (AIOS) – Security and Firewall plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 5.2.6. This is due to missing or incorrect nonce validation on the render_404_detection() function. This makes it possible for unauthenticated attackers to block IP addresses that triggered a 404 via a 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, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.
CWE-352: Cross-Site Request Forgery (CSRF)
All-In-One Security (AIOS) <= 5.2.6 carries this weakness at render_404_detection(), and reaching it 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 All-In-One Security (AIOS) the fix is 5.2.7: builds <= 5.2.6 are affected, anything from 5.2.7 onward is not.
Remediation
Update to version 5.2.7, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to All-In-One Security (AIOS): WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: All-In-One Security (AIOS) 5.2.7 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in All-In-One Security (AIOS) – Security and Firewall
- 9.8CVE-2016-10887: All In One WP Security & Firewall SQL Injection
CVE-2016-10887 - 9.8CVE-2016-10888: All In One WP Security & Firewall SQL Injection
CVE-2016-10888 - 9.8CVE-2015-9310: All In One WP Security & Firewall SQL Injection
CVE-2015-9310 - 9.0CVE-2015-0894: All In One WP Security & Firewall SQL Injection
CVE-2015-0894 - 7.4CVE-2014-6242: All In One WP Security & Firewall Access or CSRF
CVE-2014-6242 - 7.2CVE-2026-8438: All-In-One Security (AIOS) <= 5.4.7 Stored XSS
CVE-2026-8438 - 6.5CVE-2022-4097: All-In-One Security – Security and Firewall IP Spoofing
CVE-2022-4097 - 6.5All In One WP Security & Firewall 5.0.0 - 5.0.7 Protection Bypass
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C