---
title: "CVE-2026-123091: Vigilant WordPress plugin - Authentication Bypass"
description: "Vigilant WordPress plugin < 2.11.0 contains a broken authentication caused by lack of two-factor enforcement on non-default login forms, letting attackers with user passwords bypass second factor and log in as that user."
url: https://panop.io/threat-heartbeat/CVE-2026-123091/
---

# CVE-2026-123091 Vigilant WordPress plugin - Authentication Bypass

Vigilant WordPress plugin < 2.11.0 contains a broken authentication caused by lack of two-factor enforcement on non-default login forms, letting attackers with user passwords bypass second factor and log in as that user.

CVSS base score 7.5 /10

High

CISA KEV

Not listed

Public exploit

None known

Authentication

Required

EPSS

0.23% chance of exploitation in 30 days

[View the NVD record ↗](https://nvd.nist.gov/vuln/detail/CVE-2026-123091)

## Details

Type

Authentication Bypass

Impact

Broken Authentication

CVSS vector

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Published

9 November 2026

Updated

11 November 2026

Weakness

[CWE-287](https://cwe.mitre.org/data/definitions/287.html)

## Vendor fix

Upgrade to version 2.11.0 or later.

Patching closes this CVE. It does not tell you which of your systems run the affected version, or what else is exposed alongside them.

## References

- [https://nvd.nist.gov/vuln/detail/CVE-2026-123091](https://nvd.nist.gov/vuln/detail/CVE-2026-123091)
- [https://wpscan.com/vulnerability/df65184a-9223-42de-8b4d-53ff427a9874/](https://wpscan.com/vulnerability/df65184a-9223-42de-8b4d-53ff427a9874/)

[← All CVEs](https://panop.io/threat-heartbeat/)

## What this record can't tell you

- Whether you run the affected software, and where
- Whether an attacker can actually reach and exploit it
- The misconfigurations that never get a CVE number
- What it would cost the business, ranked into what to fix first

Panop answers these inside your environment, for this CVE and every other finding.

[Book a demo](https://panop.io/demo)
