Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain victim WordPress password
-
DeliveryInitiate 2FA login flow
-
ExploitRotate client-supplied rate-limit identifier (or target unprotected endpoint)
-
ExecutionAutomate OTP brute-force across full 6-digit space
-
PersistSubmit valid OTP code
-
ImpactAuthenticate as victim with full account privileges
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Authentication mechanism validation
MITRE ATT&CK
2 techniques across 2 tactics: Defense Evasion, Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | The attacker must already possess the target account's WordPress password - this is the primary prerequisite and is captured by AC:H in the CVSS vector. The miniOrange 2FA plugin must be installed, active, and running a vulnerable version (below 6.3.1 in the 6.x branch or below 19.3 in the 18.x/19.x branch). 2FA must be enabled for the target account. No user interaction is required once credentials are in hand. Exploitation is limited to accounts where 2FA is enforced via this specific plugin; accounts without 2FA or using a different 2FA plugin are unaffected. Network access to the WordPress login endpoints is required. |
| Impact | The CVSS 3.1 vector AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H scores 7.5 (High). AC:H correctly reflects the prerequisite of having the victim's password; however, PR:L is questionable - the attacker is not authenticated to any account, and the password-knowledge prerequisite is more accurately captured by AC:H than by a privilege level. C:H/I:H/A:H is justified because successful 2FA bypass yields full WordPress account takeover. A publicly available WPScan proof-of-concept elevates real-world risk well above what the CVSS score alone might suggest. No KEV listing is present, indicating no confirmed mass exploitation at time of analysis, but the PoC reduces the skill barrier significantly. EPSS data is not provided; given the WordPress ecosystem's size and the availability of public exploit code, opportunistic exploitation targeting WordPress admin accounts is a realistic near-term concern. The attack is conditional on prior credential compromise, making credential hygiene and breach-monitoring a meaningful compensating layer. |
| Exploit ScenarioDerived | An attacker obtains a victim's WordPress credentials via phishing or a credential-dump leak, then initiates a login attempt against the 2FA-protected account. By scripting OTP submission against the unrate-limited validation endpoint - or by rotating the client-supplied identifier between attempts on the rate-limited endpoint - the attacker exhausts the 6-digit TOTP space within seconds to minutes, bypassing 2FA entirely. The publicly available WPScan PoC confirms this workflow is readily automatable. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 10, 2026
Two-factor authentication bypass in the miniOrange 2FA WordPress plugin allows an attacker who has already obtained a victim's password to defeat the second factor through unlimited OTP brute-forcing. The plugin keys its attempt-rate limit to a client-controlled identifier rather than the target account, enabling an adversary to rotate that identifier and circumvent lockout entirely; a separate validation endpoint applies no rate limit at all. A publicly available exploit (WPScan) confirms practical exploitability against plugin versions below 6.3.1 and 19.3.
RemediationAI
Update the miniOrange 2FA WordPress plugin to version 6.3.1 or higher (for 6.x installations) or version 19.3 or higher (for 18.x/19.x installations); vendor-released patches are confirmed available. Consult the WPScan advisory at https://wpscan.com/vulnerability/e1e57673-18cb-4157-9d58-547af7101b04/ for patch confirmation. As a compensating control prior to patching, consider enforcing IP-based rate limiting at the WAF or hosting layer for the WordPress login and OTP validation endpoints - be aware this may affect legitimate users on shared IPs or VPNs. Additionally, enabling breach-detection or alerting on repeated failed login attempts at the server level can surface active brute-force attempts. Deactivating the plugin until it is patched is the most effective short-term control, but this removes 2FA protection entirely and should only be considered if an alternative 2FA solution can be deployed immediately.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
miniOrange 2FA is a WordPress authentication plugin that adds TOTP/OTP-based second-factor verification to the WordPress login flow. The root cause (CWE-287: Improper Authentication) manifests in two places: first, the OTP attempt counter is bound to an attacker-supplied session or device identifier rather than the account under attack, so rotating that identifier resets the counter; second, a separate OTP validation endpoint enforces no rate limit whatsoever. TOTP codes are 6-digit values cycling every 30 seconds, yielding a search space of at most one million values per window - trivially exhaustible without rate limiting. Affected CPE: cpe:2.3:a:unknown:miniorange_2fa (vendor field erroneous; actual vendor is miniOrange). Affected version ranges: 6.x before 6.3.1 and 18.x-19.x before 19.3.
Know when Miniorange 2fa gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Attacker is unauthenticated (PR:N); prior password knowledge is a prerequisite condition captured by AC:H; full account takeover justifies C:H/I:H/A:H.
Primary rating from Vendor (WPScan).
CVSS VectorVendor: WPScan
Lifecycle Timeline
3DescriptionCVE.org
The miniOrange 2FA WordPress plugin before 6.3.1, miniOrange 2FA WordPress plugin before 19.3 does not scope its second-factor attempt limit to the account being attacked, keying it instead to an identifier the client supplies and can change at will, allowing an attacker who already knows a victim's password to make unlimited one-time-passcode guesses and defeat the second factor. A second validation endpoint applies no attempt limit at all.
Technical POC Analysis
CWE-287 (Improper Authentication).
Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.
Executive ViewAI
WordPress sites using miniOrange 2FA plugin versions below 6.3.1 and 19.3 can have their two-factor authentication bypassed through OTP brute-force attacks. Attackers exploiting publicly available proof-of-concept code can defeat the second authentication factor, potentially leading to account takeover and unauthorized access to protected WordPress environments.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
More in Miniorange 2fa
View allUnauthenticated arbitrary site-option deletion in the miniOrange 2FA WordPress plugin (versions 5.3.24 through before 6.
Two-factor authentication is completely bypassable in the miniOrange 2FA WordPress plugin before version 6.2.6, enabling
miniOrange 2FA versions 6.2.9 to before 6.3.1 permit an attacker who already knows a victim's WordPress password to add
Account takeover in the miniOrange 2FA WordPress plugin before 6.2.7 is enabled when an attacker already possesses a tar
Cross-Site Request Forgery (CSRF) vulnerability in Drupal Enterprise MFA - TFA for Drupal allows Cross Site Request Forg
Missing authorization in the miniOrange 2FA WordPress plugin before 6.2.7 allows any authenticated low-privileged user t
Authentication Bypass Using an Alternate Path or Channel vulnerability in Drupal Enterprise MFA - TFA for Drupal allows
Authentication Bypass Using an Alternate Path or Channel vulnerability in Drupal Enterprise MFA - TFA for Drupal allows
Missing Authorization vulnerability in Drupal Enterprise MFA - TFA for Drupal allows Forceful Browsing.0.0 before 4.7.0,
Authentication Bypass by Capture-replay vulnerability in Drupal Enterprise MFA - TFA for Drupal allows Remote Services w
Authentication Bypass Using an Alternate Path or Channel vulnerability in Drupal Enterprise MFA - TFA for Drupal allows
EUVD-2026-75264
GHSA-fg24-3rh9-37gf
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB