Skip to main content
CVE-2026-123091VulnerabilityPublished

The Vigilant WordPress plugin before 2.11.0 does not enforce its two-factor authentication on login forms other than

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-123091· High

Not known to be exploited : upgrade to 2.11.0 soon.

Data as of 9 Nov 2026, 10:32 UTC

Severity
High

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

  1. Disclosed: evidence found.

    CVE published 9 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
VigilantAffected
  • <2.11.0
Fixed in
  • 2.11.0

AI-suggested

Upgrade the Vigilant WordPress plugin to version 2.11.0 or later, where this issue is fixed. No other mitigation is indicated by the available data.

Description

The Vigilant WordPress plugin versions before 2.11.0 fail to enforce two-factor authentication (2FA) on login forms other than the default WordPress login form. This allows an attacker who has obtained a user's password to bypass the second authentication factor and gain access to the user's account.

References

Community reviews

Loading reviews…