CVE-2026-104732 — WordPress
CRITICALCVE-2026-104732 is a critical-severity (CVSS 9.8) Improper Authentication vulnerability. No vendor fix is recorded yet; mitigation options are listed below.
The Advanced IP Blocker plugin for WordPress is vulnerable to Authentication Bypass in all versions up to, and including, 8.13.13 The vulnerability exists because `handle_login_action()`…
Description
The Advanced IP Blocker plugin for WordPress is vulnerable to Authentication Bypass in all versions up to, and including, 8.13.13 The vulnerability exists because handle_login_action() performs no server-side check — via transient, session marker, or equivalent — that a requester completed step-1 password authentication before processing a step-2 TOTP submission for the POSTed user_id; compounding this, an error branch in the function unconditionally mints a fresh advaipbl-2fa-interim-{user_id} nonce and delivers it in a Location header to any unauthenticated caller, after which display_2fa_login_form_step_2() renders a valid advaipbl-2fa-verify-{user_id} nonce in HTML — both nonces computed against a fixed uid=0 empty-session context and therefore fully reusable by the attacker across subsequent requests. This makes it possible for unauthenticated attackers to bypass authentication entirely for any 2FA-enabled account, including administrators, by brute-forcing an unthrottled 6-digit TOTP code (no attempt counter, no account lockout, and no wp_login_failed firing) and receiving a fully authenticated session cookie via wp_set_auth_cookie without ever supplying the account password, resulting in complete site takeover. Exploitation requires only a known user_id for an account that has the plugin's 2FA feature enabled.
Detection & mitigation playbook
VulnerabilityDetect
Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).
Remediation status
No fixed release is recorded for CVE-2026-104732 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.
Mitigate without a patch
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
Frequently Asked Questions
Is CVE-2026-104732 in your dependencies?
Find it across , including transitive dependencies.