Defender Security <= 2.4.6 - Cross-Site Request Forgery Bypass
Strategic Overview
- Status
- Patched in 2.4.6.1
- Affected Version
<= 2.4.6- CVSS
- 4.3Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2021-4425
At a glance
CVE-2021-4425 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Defender Security WordPress plugin, affecting versions <= 2.4.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 2.4.6.1; sites on affected versions should update now. Disclosed March 2021, reported by Jerome Bruandet.
Vulnerability Overview
The Defender Security plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 2.4.6. This is due to missing or incorrect nonce validation on the verify_otp_login_time() function. This makes it possible for unauthenticated attackers to verify a one time login 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)
Defender Security <= 2.4.6 carries this weakness at verify_otp_login_time(), 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 Defender Security the fix is 2.4.6.1: builds <= 2.4.6 are affected, anything from 2.4.6.1 onward is not.
Remediation
Update to version 2.4.6.1, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Defender Security: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Defender Security 2.4.6.1 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in Defender Security – Malware Scanner, Login Security & Firewall
- 7.5CVE-2022-44581: Defender Security <= 3.3.2 Info Disclosure
CVE-2022-44581 - 7.2CVE-2026-19225: Defender Security RCE
CVE-2026-19225 - 6.5CVE-2024-25595: Defender Security <= 4.4.1 IP Address Spoofing
CVE-2024-25595 - 5.3CVE-2024-37444: Defender Security <= 4.7.2 Missing Authorization
CVE-2024-37444 - 5.3CVE-2023-51490: Defender Security <= 4.1.0 Info Exposure
CVE-2023-51490 - 5.3CVE-2023-47189: Defender Security Masked Login Area Security Feature
CVE-2023-47189 - 5.3CVE-2023-5089: Defender Security Hide Login Page Feature Protection
CVE-2023-5089
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C