CVE-2026-123091: Vigilant (WordPress plugin) · Improper Authentication
Affects Vigilant (WordPress plugin)Source CVE Database V5
Not known to be exploited : upgrade to 2.11.0 soon.
Data as of 9 Nov 2026, 06:35 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 2.11.0
Exploitation evidence
Disclosed: evidence found.
CVE published 9 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 8 Nov 2026.
What to do
Upgrade Vigilant (WordPress plugin) to 2.11.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Vigilant | Affected
| Fixed in
|
AI-suggested
Upgrade the Vigilant plugin to version 2.11.0 or later, where this vulnerability is fixed. No other mitigation is required as the official fix enforces two-factor authentication on all login forms.
Description
The Vigilant WordPress plugin before version 2.11.0 has an improper authentication vulnerability where its two-factor authentication (2FA) is not enforced on login forms other than the default WordPress login form. This allows an attacker who knows a user's password to bypass the second authentication factor and gain access as that user.