# CVE-2026-77771: miniOrange 2FA (Free & Pro) - 2FA Bypass via Session-Scoped OTP Lockout

> Attackers with valid passwords can bypass two-factor authentication by manipulating session identifiers to make unlimited OTP guesses.

- **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:** 10 Sep 2026
- **Updated:** 10 Sep 2026
- **Also known as:** GHSA-fg24-3rh9-37gf

## What is CVE-2026-77771?

CVE-2026-77771 is a high-severity authentication bypass vulnerability in Unknown miniOrange 2FA, published on 10 Sep 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.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.

Weakness: CWE-287 (Improper Authentication)

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


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

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

## Is CVE-2026-77771 being exploited?

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

Public exploit code:

- In the miniOrange 2FA WordPress plugin (versions before 6.3.1 and 19.3), the two-factor authentication (2FA) attempt limit is flawed. (github_poc): https://github.com/pervinzahidli/CVE-2026-77771

## Fix prompt for AI coding agents

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

What it is: CVE-2026-77771 is a high-severity authentication bypass vulnerability in Unknown miniOrange 2FA, published on 10 Sep 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-77771 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-77771/ (Markdown: https://insights.sbomify.com/CVE-2026-77771/index.md)
```

## Sources

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

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