Summary
CVE-2026-86710 is a critical authentication bypass vulnerability (CVSS 9.8) in the Login with QR WordPress plugin, affecting all versions up to and including 1.0.0. The plugin fails to verify that a QR login code was actually issued by the site, instead matching the attacker-supplied autologin_code parameter against any stored user metadata value. This allows a completely unauthenticated remote attacker to log in as any user, including site administrators.
Technical details
- Root cause: The plugin’s QR-based passwordless login flow does not cryptographically validate that a submitted login code was legitimately issued to a session; it instead performs a loose lookup of the
autologin_coderequest parameter against arbitrary stored user metadata. - Trigger conditions: An attacker only needs to identify or guess a value present in a target user’s metadata and submit it as the
autologin_codeparameter to the plugin’s login handler — no valid QR code, credentials, or prior authentication is required. - Attack vector: Remote, over the network (AV:N), with low attack complexity, no privileges required, and no user interaction (PR:N/UI:N) — making the flaw trivially exploitable at scale against internet-facing WordPress sites.
- Impact: Full authentication bypass leading to complete account takeover, including administrator accounts, resulting in loss of confidentiality, integrity, and availability of the WordPress site (C:H/I:H/A:H). A successful attacker can install malicious plugins/themes, plant backdoors, exfiltrate data, or fully deface/take down the site.
Affected software
- Login with QR (WordPress plugin) — all versions through 1.0.0
Severity
- CVSS v3.1 Base Score: 9.8 (Critical)
- Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Mitigation and recommended actions
- Immediate: As of this writing, no patched version of Login with QR has been released. Sites should immediately deactivate and uninstall the Login with QR plugin until a fixed release is available.
- If no patch: If the plugin cannot be removed immediately, restrict or block access to the plugin’s autologin/QR login endpoint at the network or web application firewall (WAF) layer, and monitor authentication logs for unexpected administrator logins or use of the
autologin_codeparameter. Rotate credentials and audit user accounts for unauthorized changes if the plugin has been in use, since exploitation leaves no requirement for valid credentials.

