Vigilant <= 2.10.0 — Two-Factor Authentication Bypass
CVE-2026-123091Published · Updated Action summary
Affected: ≤2.10.0Update to 2.11.0 or newer
All remediation steps- Severity
- Medium4.3
- CVSS
- 4.3CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:NWhat does this vector mean?
AV:NAttack vector- Network
AC:LAttack complexity- Low
PR:LPrivileges required- Low
UI:NUser interaction- None
S:UScope- Unchanged
C:NConfidentiality- None
I:LIntegrity- Low
A:NAvailability- None
- Weakness
- CWE-287 Improper Authentication
- Required access
- Unknown
- Exploit prediction (EPSS)
- 0.2% chance in 30 days14th percentile
- CISA KEV
- Not listed
On this page8
Am I affected?
Vigilant – 100% Free Security Suite: Firewall, 2FA, Login, Headers, Scanner… vigilante
- Affected≤ 2.10.0
- Patched in2.11.0
Update to 2.11.0 or newer.
You are affected if you run ≤ 2.10.0. Version 2.11.0 and later are not affected by this issue.
- Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under Vigilant – 100% Free Security Suite: Firewall, 2FA, Login, Headers, Scanner….
- No admin access? Run a passive check of your site. It reads public files only.
What to do
- Update to version 2.11.0, or a newer patched version
- Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
- Watch Vigilant – 100% Free Security Suite: Firewall, 2FA, Login, Headers, Scanner… to get an email when the next vulnerability is published.
Advisory
Source description from Wordfence Intelligence, credited to Fernando Tellado.
The Vigilant plugin for WordPress is vulnerable to Two-Factor Authentication Bypass in all versions up to, and including, 2.10.0. This is due to a shortcut in the authenticate filter that returned the authenticated user object whenever the request carried action=vigilante_2fa, a valid nonce and a pending token — all values available to anyone who knows the account password. This makes it possible for unauthenticated attackers to bypass two-factor authentication on any login form that calls wp_signon() (such as WooCommerce checkout), completing authentication with only a valid password. A site must use a login form other than the default WordPress wp-login.php that calls wp_signon() internally, such as WooCommerce.
Exploits & references
Proof-of-concept & detection
No public proof-of-concept or detection template is known for this vulnerability.
Advisories & patches
- Advisorywordfence.com
Related CVEs
More in Vigilant – 100% Free Security Suite: Firewall, 2FA, Login, Headers, Scanner…
All 2| Severity | Vulnerability | CVE | Published |
|---|---|---|---|
| High7.2 | Unauthenticated Stored Cross-Site Scripting ≤2.10.2Update to 2.10.3 | CVE-2026-81754 |
- High7.2Unauthenticated Stored Cross-Site Scripting
≤2.10.2Update to 2.10.3
Timeline
CVE published
Severity medium, CVSS 4.3
Record last updated
Sources & licenses
Wordfence record- Vulnerability data
- Wordfence Intelligence. Copyright 2012-2026 Defiant Inc. Licensed under the CC BY-SA 4.0.
- CVE® identifiers
- Copyright 1999-2026 The MITRE Corporation. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
- CVSS / CWE
- National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
- EPSS
- Exploit Prediction Scoring System by FIRST.org.
- VulnCrest content
- Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.