HomeWordPress vulnerabilitiesDefender Security
Defender Security vulnerabilities
Defender Security has 4 known vulnerabilities in this database. The most recent published record is dated 27 Aug 2026.
- Known vulnerabilities
- 4
- Active installs
- 80,000+
- Latest version
- 6.3.0
- Last updated
- 29 Sep 2026
- Most recent
- 27 Aug 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Remote code execution CVE-2026-19225 | Medium 6.6 | Before 6.2.0 | Fixed in 6.2.0 | 27 Aug 2026 |
| Broken access control CVE-2024-37444 | Medium 5.3 | Before 4.7.3 | Fixed in 4.7.3 | 1 Nov 2024 |
| Security weakness CVE-2023-5089 | Medium 5.3 | Before 4.1.0 | Fixed in 4.1.0 | 16 Oct 2023 |
| Cross-site request forgery (CSRF) CVE-2021-4425 | Medium 4.3 | Up to 2.4.6 | Fixed in a later version (latest 6.3.0) | 12 Jul 2023 |
Read the published descriptions
- CVE-2026-19225, 27 Aug 2026
- The Defender Security WordPress plugin before 6.2.0 does not restrict a network-wide setting to network administrators, allowing an administrator of any single site on a multisite network to execute arbitrary code across the entire network. CVE record
- CVE-2024-37444, 1 Nov 2024
- Missing Authorization vulnerability in WPMU DEV - Your All-in-One WordPress Platform Defender Security defender-security.This issue affects Defender Security: from n/a through <= 4.7.1. CVE record
- CVE-2023-5089, 16 Oct 2023
- The Defender Security WordPress plugin before 4.1.0 does not prevent redirects to the login page via the auth_redirect WordPress function, allowing an unauthenticated visitor to access the login page, even when the hide login page functionality of the plugin is enabled. CVE record
- CVE-2021-4425, 12 Jul 2023
- 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. CVE record
What to do if you run Defender Security
If you run Defender Security, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Defender Security vulnerabilities
Free. We email you when a new vulnerability is published for Defender Security, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.