CVE-2026-16035

miniOrange 2FA < 6.2.7 - Subscriber+ Arbitrary-Recipient OTP Send

Published Aug 4, 2026 CVSS 3.1 · 4.3 Medium EPSS < 1% KEV · Not listed
Description
The miniOrange 2FA WordPress plugin before 6.2.7 does not restrict who can trigger its second-factor configuration OTP send, nor bind the OTP recipient to the enrolling user's own address, allowing a low-privileged user to send one-time-passcode emails to arbitrary recipients and to exhaust the site's metered OTP allowance, preventing legitimate users from receiving their second-factor codes.

Analysis

AI-generated

Technical impact

The miniOrange 2FA WordPress plugin version 6.2.6 and earlier fails to verify that a user is permitted to request a one‑time‑password (OTP) and sends the generated OTP to the email address supplied by the attacker. This flaw, a missing authorization (CWE‑862), allows a low‑privileged user to cause OTP emails to be sent to arbitrary recipients, thereby leaking the OTP to untrusted parties and exhausting the site’s metered OTP quota, which in turn blocks legitimate users from obtaining the OTP required for second‑factor authentication.

Affected Systems

Vendors and products affected include the miniOrange 2FA WordPress plugin when its version is 6.2.6 or earlier. No specific product version list is available beyond the critical threshold of 6.2.7.

Risk and Exploitability

The CVSS score of 4.3 indicates a moderate severity. The EPSS score of < 1% suggests that exploitation is currently considered unlikely, and the vulnerability is not listed in the CISA KEV catalog. Nevertheless, the flaw can be exploited by any active WordPress user with access to the site’s backend or front‑end, as the plugin accepts HTTP requests to trigger the OTP send function. Because the attack does not require elevated privileges or complex setup, the risk of exploitation remains notable in environments where the plugin is installed and the user base is not tightly controlled. The vulnerability can be triggered via a straightforward web request to the plugin’s settings endpoint, making it a low‑barrier attack vector.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the miniOrange 2FA plugin to version 6.2.7 or later, which implements proper authorization checks to restrict OTP requests to privileged users.
  • Disable or revoke the ability of non‑administrative roles to send OTPs, either by configuring the plugin settings or using a role‑based access control plugin until the patch is applied.
  • Monitor the OTP usage logs for unusual patterns of OTP requests and consider temporarily throttling or blocking the OTP send endpoint to prevent exhaustion of the site’s OTP quota during remediation.

Generated by OpenCVE AI on August 4, 2026 at 20:48 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Miniorange
Miniorange miniorange 2fa
Wordpress
Wordpress wordpress
Vendors & Products Miniorange
Miniorange miniorange 2fa
Wordpress
Wordpress wordpress
Type Values Removed Values Added
Weaknesses CWE-862
Metrics cvssV3_1

{'score': 4.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L'}

ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description The miniOrange 2FA WordPress plugin before 6.2.7 does not restrict who can trigger its second-factor configuration OTP send, nor bind the OTP recipient to the enrolling user's own address, allowing a low-privileged user to send one-time-passcode emails to arbitrary recipients and to exhaust the site's metered OTP allowance, preventing legitimate users from receiving their second-factor codes.
Title miniOrange 2FA < 6.2.7 - Subscriber+ Arbitrary-Recipient OTP Send
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
WPScan
Published
Updated
Aug 4, 2026, 5:37 PM
Reserved
Jul 17, 2026, 9:01 AM
Status
Deferred
Published
Aug 4, 2026, 7:16 AM
Modified
Aug 26, 2026, 4:31 PM