Quick answers
- Is CVE-2026-111949 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-111949 being exploited in the wild.
- How severe is CVE-2026-111949?
- Informational severity, published 21 October 2026.
- Which products and versions are affected?
- miniOrange 2FA before 6.3.1.
- Is there a fix for CVE-2026-111949?
- Yes: fixed in 6.3.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-111949 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-111949?
- Check whether you run miniOrange 2FA at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 6.3.1
Technical details
The vulnerability is an authentication bypass in the passkey registration flow: the plugin fails to restrict additional passkey registration when a passkey-based login is pending, allowing an attacker with password knowledge to add their own authenticator via CWE-287 (Improper Authentication). The attacker must have obtained the user's password through other means and have network access to the WordPress installation; the attack requires no user interaction. The fix is available in version 6.3.1.
Affected products
- miniOrange 2FA before 6.3.1
Timeline
- 2026-10-21: disclosed
- 2026-10-19: other: added to WPScan vulnerability database