Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-104732 critical CVSS 9.8

Authentication Bypass in Advanced IP Blocker (WordPress plugin) (CVE-2026-104732)

Summary

Authentication bypass in Advanced IP Blocker (WordPress plugin) (CVE-2026-104732). Successful exploitation can lead to full system takeover. Exploitable via user_id.

Original description

The description as published by the source.

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.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-104732 has been found in Advanced IP Blocker (WordPress plugin).
Attackers can target a specific entry point like user_id over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.8/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Advanced IP Blocker (WordPress plugin) CVE-2026-104732" on the vendor's site.

CVE-2026-104732 (Advanced IP Blocker (WordPress plugin)) — CWE-287 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: user_id / Location / wp_login_failed / wp_set_auth_cookie
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Authentication bypass (CWE-287) exists in Advanced IP Blocker (WordPress plugin). Attackers reach the vulnerable code path via user_id without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of Advanced IP Blocker (WordPress plugin). Attack surface: user_id / Location / wp_login_failed / wp_set_auth_cookie.

🔥 Severity

Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで Advanced IP Blocker (WordPress plugin) を使っているサービスとバージョンを洗い出す。

  2. 2
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details