CVE-2026-111949 miniOrange 2FA 6.2.9 - 6.3.0 - 2FA Bypass via Passkey Second-Factor Rebinding
High 7.5
Published
Updated
Check this codebase for CVE-2026-111949 and fix it if it is affected.
What it is: CVE-2026-111949 is a high-severity vulnerability in Unknown miniOrange 2FA, published on 21 Oct 2026.
Exploitation: There is no known exploitation of CVE-2026-111949 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-111949/ (Markdown: https://insights.sbomify.com/CVE-2026-111949/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-111949?
CVE-2026-111949 is a high-severity vulnerability in Unknown miniOrange 2FA, published on 21 Oct 2026.
Official description
The miniOrange 2FA WordPress plugin before 6.3.1 does not prevent a pending passkey login from registering an additional passkey on an account that already has one configured, allowing an attacker who knows a user's password to add their own authenticator and bypass the second factor.
Weakness: CWE-287
Which versions are affected by CVE-2026-111949?
How do I fix CVE-2026-111949?
No fix has been published for CVE-2026-111949 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-111949 being exploited?
There is no known exploitation of CVE-2026-111949 in the wild and no public exploit code.
Sources
Also known as GHSA-79v7-2xfm-2p77.