---
id: "CVE-2026-111739"
kind: "vulnerability"
aliases: ["CVE-2026-111739"]
title: "WordPress 2FA plugins: attacker's own code can unlock a victim's session"
severity: "high"
cvss: null
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["package", "self-hosted", "two-factor-auth", "wordpress"]
not_affected_if: ["managed-hosting-with-other-2fa", "no-2fa-plugin"]
published_at: "2026-10-29T06:17:18+00:00"
first_seen_at: "2026-10-29T06:53:13+00:00"
updated_at: "2026-10-29T06:54:51+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-111739", "first_seen_at": "2026-10-29T06:53:13+00:00"}]
---

# WordPress 2FA plugins: attacker's own code can unlock a victim's session

The Two Factor Authentication and All-In-One Security WordPress plugins do not check that the two-factor code belongs to the account being logged into. An attacker who knows a victim's password can pass the second factor with their own account's code and take over the victim's session.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed version of the Two Factor Authentication plugin; affected if below `1.17.0`.
- Check the installed version of the All-In-One Security (AIOS) plugin; affected if below `5.5.0`.

## Timeline

- 2026-10-29T06:53:13+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-111739

## From the sources

The Two Factor Authentication WordPress plugin before 1.17.0, All-In-One Security (AIOS)  WordPress plugin before 5.5.0 do not bind the account whose two-factor code is verified to the account being authenticated, allowing an attacker who knows a victim's password and holds their own two-factor-enabled account to satisfy the victim's second-factor check with their own code and obtain the victim's session.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_