# CVE-2026-12695: miniOrange 2FA < 6.2.6 - 2FA Bypass via Attacker-Controlled ga_secret

> Unauthenticated attackers can bypass two-factor authentication in miniOrange 2FA by supplying a controlled secret, gaining access to victim accounts.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Jul 2026
- **Updated:** 31 Jul 2026
- **Also known as:** GHSA-24j9-5c5r-9c88

## What is CVE-2026-12695?

CVE-2026-12695 is a high-severity authentication bypass vulnerability in Unknown miniOrange 2FA, published on 31 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The miniOrange 2FA  WordPress plugin before 6.2.6 does not validate the submitted one-time password against the targeted user's stored secret, instead verifying it against an attacker-supplied value, allowing an unauthenticated attacker who knows a victim's password to bypass two-factor authentication and gain access to the victim's account, including administrators.

Weakness: CWE-287 (Improper Authentication)

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


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

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

## Is CVE-2026-12695 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-12695 is a high-severity authentication bypass vulnerability in Unknown miniOrange 2FA, published on 31 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-12695 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-12695/ (Markdown: https://insights.sbomify.com/CVE-2026-12695/index.md)
```

## Sources

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

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