Shield Security – Smart Bot Blocking & Intrusion Prevention Security <= 19.1.13 - Cross-Site Request Forgery
Strategic Overview
- Status
- Patched in 19.1.11
- Affected Version
<= 19.1.10- CVSS
- 4.3Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2024-4344
At a glance
CVE-2024-4344 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Shield Security WordPress plugin, affecting versions <= 19.1.10. 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 19.1.11; sites on affected versions should update now. Disclosed June 2024, reported by Christian Angel.
Vulnerability Overview
The Shield Security – Smart Bot Blocking & Intrusion Prevention Security plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 19.1.13. This is due to missing or incorrect nonce validation on the exec function. This makes it possible for unauthenticated attackers to disable pin protection for the admin interface of the plugin 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)
Reaching this weakness in Shield Security <= 19.1.10 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 Shield Security the fix is 19.1.11: builds <= 19.1.10 are affected, anything from 19.1.11 onward is not.
Remediation
Update to version 19.1.11, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Shield Security: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Shield Security 19.1.11 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in Shield Security – Smart Bot Blocking, Brute-Force Login Protection & File Scanning
- 9.8CVE-2023-6989: Shield Security LFI
CVE-2023-6989 - 7.2CVE-2024-22163: Shield Security <= 18.5.7 Stored Cross-Site Scripting
CVE-2024-22163 - 7.2CVE-2023-0992: Shield Security <= 17.0.17 Stored Cross-Site Scripting
CVE-2023-0992 - 6.5CVE-2026-0722: Shield Security <= 21.0.8 CSRF to SQL Injection
CVE-2026-0722 - 6.1CVE-2026-0561: Shield Security <= 21.0.8 Reflected XSS
CVE-2026-0561 - 6.1CVE-2024-7313: Shield Security Reflected XSS
CVE-2024-7313 - 5.5CVE-2022-0211: Shield Security <= 13.0.5 Admin+ Stored XSS
CVE-2022-0211 - 4.3CVE-2025-14427: Shield Security Authenticated (Subscriber+) Email MFA
CVE-2025-14427
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C