CVE-2026-119040: Defender Security (WordPress plugin) · Improper Authentication
Affects Defender Security (WordPress plugin)Source CVE Database V5
Not known to be exploited : upgrade to 6.4.1 soon.
Data as of 12 Nov 2026, 06:20 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 6.4.1
Exploitation evidence
Disclosed: evidence found.
CVE published 12 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 11 Nov 2026.
What to do
Upgrade Defender Security (WordPress plugin) to 6.4.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Defender Security | Affected
| Fixed in
|
AI-suggested
Upgrade the Defender Security plugin to version 6.4.1 or later, where this vulnerability has been fixed. Applying this official fix will enforce limits on failed two-factor authentication attempts and prevent brute-force bypass of the second factor.
Description
The Defender Security WordPress plugin versions before 6.4.1 have an improper authentication vulnerability where the plugin does not limit the number of failed two-factor authentication attempts by default. This allows an attacker who already knows a user's password to brute-force the one-time code, potentially bypassing the second factor of authentication.