miniOrange 2FA – Two Factor Authentication for WordPress (OTP, SMS, Email, Google Authenticator) 6.2.9 - 6.3.0 - Two-Factor Authentication Bypass
Strategic Overview
- Status
- Patched in 6.3.1
- Affected Plugin
- miniOrange 2FA – Two Factor Authentication for WordPress (OTP, SMS, Email, Google Authenticator)
- Affected Version
6.2.9 – 6.3.0- CVSS
- 4.3Medium
- Weakness type
- CWE-287 · Improper Authentication
- CVE
CVE-2026-111949
At a glance
CVE-2026-111949 is a medium-severity Improper Authentication vulnerability in the miniOrange 2FA WordPress plugin, affecting versions 6.2.9 – 6.3.0. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). The issue is fixed in version 6.3.1; sites on affected versions should update now. Disclosed October 2026, reported by RIA Labs.
Vulnerability Overview
The miniOrange 2FA – Two Factor Authentication for WordPress (OTP, SMS, Email, Google Authenticator) plugin for WordPress is vulnerable to Two-Factor Authentication Bypass in versions 6.2.9 through 6.3.0. This is due to missing check on whether the requesting session is a fully authenticated dashboard session before allowing passkey registration on accounts that already have 2FA configured, allowing a mid-login (pending) session to add a new passkey. This makes it possible for authenticated attackers, with subscriber-level access and above, to add their own passkey authenticator to a victim account during a pending login session, then complete authentication as that user without possessing the legitimate second factor. The attacker must know the target user's password, and the target account must have a passkey already configured as the second factor.
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 interaction from a victim user.
CWE-287: Improper Authentication
Reaching this weakness in miniOrange 2FA 6.2.9 – 6.3.0 takes a caller who can reach the endpoint. 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 6.3.1: builds 6.2.9 – 6.3.0 are affected, anything from 6.3.1 onward is not.
Remediation
Update to version 6.3.1, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: miniOrange 2FA 6.3.1 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in miniOrange 2FA – Two Factor Authentication for WordPress (OTP, SMS, Email, Google Authenticator)
- 8.8miniOrange's Google Authenticator CSRF to Malware Scan Termination
- 8.1CVE-2022-0229: miniOrange's Google… Arbitrary Options Deletion
CVE-2022-0229 - 7.5CVE-2022-4943: miniOrange's Google… Plugin Settings Change
CVE-2022-4943 - 7.5CVE-2022-44589: miniOrange's Google… Sensitive Data Exposure
CVE-2022-44589 - 7.3CVE-2026-77770: miniOrange 2FA Unauthenticated Arbitrary Option
CVE-2026-77770 - 6.3miniOrange's Google Authenticator <= 5.5.82 Missing Authorization
- 6.1miniOrange's Google Authenticator <= 5.5.7 Reflected XSS
- 6.1miniOrange's Google Authenticator <= 5.4.39 Cross-Site Scripting
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C