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

> Low-privileged users can send OTP emails to arbitrary recipients, exhausting site quotas and blocking legitimate 2FA access.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Aug 2026
- **Updated:** 4 Aug 2026
- **Also known as:** GHSA-pq9j-g4gw-q76g

## What is CVE-2026-16035?

CVE-2026-16035 is a medium-severity missing authorization vulnerability in Unknown miniOrange 2FA, published on 4 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

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

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-16035?


## How do I fix CVE-2026-16035?

No fix has been published for CVE-2026-16035 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-16035 being exploited?

There is no known exploitation of CVE-2026-16035 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-16035 and fix it if it is affected.

What it is: CVE-2026-16035 is a medium-severity missing authorization vulnerability in Unknown miniOrange 2FA, published on 4 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-16035 in the wild and no public exploit code.

Affected product: Unknown miniOrange 2FA. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-16035/ (Markdown: https://insights.sbomify.com/CVE-2026-16035/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-16035
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-16035
- OSV: https://osv.dev/vulnerability/CVE-2026-16035

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-16035/
Summaries are generated and may contain mistakes; the official description above is the record.