# CVE-2026-16619: miniOrange 2FA < 6.2.8 - 2FA Bypass via Unlimited Second-Factor Attempts

> Attackers with valid passwords can bypass two-factor authentication by unlimited guessing of one-time codes due to flawed attempt tracking.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 6 Aug 2026
- **Updated:** 7 Aug 2026
- **Also known as:** GHSA-m749-g32x-9hgv

## What is CVE-2026-16619?

CVE-2026-16619 is a high-severity vulnerability in Unknown miniOrange 2FA, published on 6 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.8 does not correctly limit the number of second-factor verification attempts, tracking them against a client-supplied identifier that is reissued on every login, allowing an attacker who already knows a user's password to guess the one-time code without limit and take over the account.

Weakness: CWE-307 (Improper Restriction of Excessive Authentication Attempts)

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


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

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

## Is CVE-2026-16619 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-16619 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-16619 is a high-severity vulnerability in Unknown miniOrange 2FA, published on 6 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-16619 exists.

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-16619/ (Markdown: https://insights.sbomify.com/CVE-2026-16619/index.md)
```

## Sources

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

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