CVE-2026-77771

miniOrange 2FA – Two Factor Authentication for WordPress (OTP, SMS, Email, Google Authenticator) 6.2.8 - 6.3.0 - Unauthenticated Second Factor Authentication Bypass

2026-09-08 00:00
pervinzahidli

Strategic Overview

Status
Patched in 19.3
Affected Version
6.2.8 – 19.2 · 2 branches
CVSS
5.3Medium
Weakness type
CWE-287 · Improper Authentication
CVE
CVE-2026-77771
View all miniOrange 2FA – Two Factor Authentication for WordPress (OTP, SMS, Email, Google Authenticator) vulnerabilities

At a glance

CVE-2026-77771 is a medium-severity Improper Authentication vulnerability in the miniOrange 2FA WordPress plugin, affecting versions 6.2.8 – 19.2 · 2 branches. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 19.3; sites on affected versions should update now. Disclosed September 2026, reported by pervinzahidli.

Vulnerability Overview

The miniOrange 2FA – Two Factor Authentication for WordPress (OTP, SMS, Email, Google Authenticator) plugin for WordPress is vulnerable to 2FA Bypass in versions 6.2.8 to 6.3.0. This makes it possible for unauthenticated attackers to bypass 2FA protection.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.

CWE-287: Improper Authentication

Reaching this weakness in miniOrange 2FA 6.2.8 – 19.2 · 2 branches takes no account at all. Improper authentication means the mechanism that proves who a caller is can be satisfied without the secret it was supposed to require.

An attacker authenticates as another user — administrators included — without ever knowing a password, so password policies and login rate limits never come into play. For miniOrange 2FA the fix is 19.3: builds 6.2.8 – 19.2 · 2 branches are affected, anything from 19.3 onward is not.

Remediation

Update to one of the following versions, or a newer patched version: 19.3, 6.3.1

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: miniOrange 2FA 19.3 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C