Advanced IP Blocker Flaw: Update Today

By Bug Circuit Security Team
Advanced IP Blocker Flaw: Update Today

Is your own website affected? Check it free in 2 minutes.

Passive outside check only. Nothing is attacked, no signup.

If you run the Advanced IP Blocker plugin on WordPress, update it today: versions up to and including 8.13.13 have a critical flaw that can let an attacker log in as a 2FA-protected user, even an administrator, without knowing the password.

This post is for owners of WordPress sites who use this plugin and want a clear answer without the jargon. You will get a plain-English explanation of the bug, a quick way to tell if you are affected, exact update steps (dashboard and command line), and a checklist for spotting trouble afterward.

What was reported

The flaw is tracked as CVE-2026-104732. (A CVE is a public ID number so everyone can talk about the same bug.) It was published on 2026-10-10 in the National Vulnerability Database (NVD) record.

Here is what the record says, in short:

  • Severity: Critical, with a CVSS score of 9.8 out of 10. CVSS is the standard 0 to 10 scale for how serious a bug is. See the CVSS overview from FIRST.
  • Weakness type: CWE-287, which means improper authentication. In plain words, the site can be fooled about who is logging in.
  • Attacker needs: no account and no clicks from you. The score reflects an attack over the internet with low complexity.
  • Affected versions: all versions up to and including 8.13.13.
  • NVD status: Deferred. We read that as NVD not having finished its own analysis, so treat the record as the current best summary, not the final word.

The NVD record does not list a fixed version number. We will not guess one. Update to the latest version and read the plugin's changelog (more on that below).

The flaw in plain English

Some sites use two-step login. Step 1 is your password. Step 2 is a six-digit code from an authenticator app. That code is called a TOTP (time-based one-time password). This plugin offers its own two-step login feature.

According to the NVD description, three things went wrong at once:

  1. Step 2 did not check that step 1 happened. The code that handles the six-digit check does not confirm the visitor already entered the right password. A stranger can skip straight to the code step for a chosen user ID.
  2. Security tokens were handed out too freely. WordPress uses short tokens called nonces to confirm a form request is genuine. The description says an error path gives one to any unauthenticated visitor, and that the tokens can be reused across later requests.
  3. Wrong guesses were never limited. There is no attempt counter and no account lockout. Failed tries also do not trigger the standard WordPress failed-login event, so tools watching for that event may see nothing.

A six-digit code has one million possible values. With no limit on guesses, a script can keep trying until it lands on a valid one. The description says the attacker then receives a fully logged-in session cookie, without ever supplying the password. The NVD calls the result complete site takeover.

The irony is real: a feature meant to add protection created the hole. That does not make two-step login a bad idea. It means this specific implementation had a gap, and the vendor has to close it.

Who is affected

Use this table to check your own situation.

Your situationWhat the NVD description saysWhat to do
Plugin installed, version 8.13.13 or older, plugin's 2FA turned on for some usersAffected. Those 2FA accounts, including admins, can be targeted.Update now, then run the checks below.
Plugin installed, version 8.13.13 or older, plugin's 2FA not usedThe described attack targets accounts with the plugin's 2FA enabled.Update anyway. Do not rely on a gap in the description.
Plugin version newer than 8.13.13Not covered by the affected range in the record.Confirm in the changelog that the login fix is included.
Plugin not installedNot affected by this CVE.Nothing to do for this one.

The attacker also needs to know a user_id for an account with the plugin's 2FA enabled. WordPress user IDs are usually small numbers, so do not count on that being hard to find.

How to fix it, step by step

Set aside ten to fifteen minutes.

  1. Take a backup. Use your host's backup tool or a backup plugin. Updates are normally safe, but a backup makes any problem easy to undo.
  2. Update the plugin. In your WordPress dashboard, go to Plugins > Installed Plugins, find Advanced IP Blocker, and click Update now. If you do not see an update, go to Dashboard > Updates and click Check again.
  3. Or update with WP-CLI (the command-line tool many hosts provide). The plugin's folder name is advanced-ip-blocker:
wp plugin update advanced-ip-blocker
wp plugin get advanced-ip-blocker --field=version
  1. Read the changelog. Open the plugin's page on WordPress.org and look at the Changelog tab. Confirm your installed version is newer than 8.13.13 and that the notes mention the login or 2FA fix. The NVD references also list a code change in the plugin's trunk that may show the vendor's related code changes.
  2. Test your login. Open a private browser window and log in with 2FA. Make sure you are not locked out before you close your admin session.

If you cannot update right now

Sometimes a site is locked by a host, an agency, or a custom setup. If you cannot update today, deactivate the plugin until you can. Go to Plugins > Installed Plugins and click Deactivate under Advanced IP Blocker. If you can, delete the plugin instead of only deactivating it.

There is a trade-off. While it is off, you lose its IP blocking and its 2FA. Your normal WordPress password login still works, so use a long, unique password for every admin. This is usually safer than leaving a known critical bug exposed. If you are unsure, ask your host or developer to do it for you.

Check whether anyone got in

A patch closes the door. It does not tell you if someone already walked through. Because the description says failed guesses do not fire the usual failed-login event, your login alerts may be quiet even if guessing happened. Check these directly:

  • Unknown administrators. Go to Users > All Users and filter by Administrator. Write down the account details first and take a backup. Then change the unknown account's role to Subscriber or delete it once evidence is saved, as described in our website hacked guide. Or run:
wp user list --role=administrator --fields=ID,user_login,user_email,user_registered
  • Changed admin emails. An attacker who gets in often changes an email so they can reset the password later.
  • Plugins or themes you did not install. Check Plugins and Appearance > Themes.
  • Unexpected redirects or odd pages when you visit your own site, especially from a phone or a search result.
  • Host access logs. Ask your host for logs, or look in your hosting panel. A large burst of repeated POST requests to your login page (wp-login.php) or to admin-ajax.php from one address is worth a closer look.

Then end every existing login session. This kicks out anyone holding a stolen session cookie. The simplest way is to replace the secret keys (salts) in wp-config.php with fresh ones from the official WordPress generator. Everyone, including you, will have to log in again. Finally, change the passwords of all admin accounts.

If you find signs of a break-in, do not panic and do not start deleting things at random. Follow our website hacked guide so you keep evidence and clean up in the right order.

Why this kind of bug keeps happening

Login code is a favorite target because one mistake can hand over the whole site. Security plugins are no exception. They run on every login, so a flaw in them is a flaw in your front door.

Two habits lower your risk without any special skill:

  • Turn on auto-updates for security-related plugins. In Plugins > Installed Plugins, click Enable auto-updates next to each one. Still glance at your site after big updates.
  • Remove plugins you do not use. An inactive plugin can still carry bugs, and each one adds code to keep current.

Good login design also limits guessing and ties the second step to a successful first step. The OWASP Authentication Cheat Sheet covers these ideas, including multi-factor authentication and protection against repeated guessing. Throttling guesses and tying the second step to a successful first step are the controls the NVD says were missing here.

Not sure what else is exposed?

One plugin bug is rarely the only loose end. If you want a quick outside view, run our free website security check. It is passive, needs no card or login, and flags common gaps. For a plain-English look at what an attacker can actually reach on a small site, read is my website hackable.

Key takeaways

  • Update Advanced IP Blocker now. Versions up to and including 8.13.13 are affected, and NVD rates the flaw Critical (CVSS 9.8).
  • The NVD lists no fixed version, so update to the latest release and confirm in the changelog that the login fix is included.
  • If you cannot update today, deactivate the plugin (or delete it if you can) and use strong, unique admin passwords until you can.
  • After updating, check for unknown admins, end all sessions by rotating your salts, and change admin passwords.
  • Failed guesses may not appear in login alerts, so check your users, plugins and host logs yourself.

A human look is the honest next step

An update fixes this one bug. It cannot tell you what else on your site is weak. A Bug Circuit Circuit audit is $49 one time: a real security engineer manually tests your whole site and sends a written report with severity, evidence and exact fixes. It is a focused audit for small sites, not an enterprise penetration test or a compliance certification. If you want us to also fix the high and critical issues, that is what Signal is for.

Source: NVD record for CVE-2026-104732.

Want certainty, not guesswork?

A real human security engineer audits your whole site by hand and sends a full report: every issue, its severity, and the exact fix. From $49, with a 14-day money-back guarantee.

See pricing

Frequently asked questions

What is the Advanced IP Blocker vulnerability?
It is CVE-2026-104732, a critical authentication bypass in the Advanced IP Blocker WordPress plugin, affecting all versions up to and including 8.13.13. The NVD says an attacker can guess the six-digit 2FA code for an account with that plugin's 2FA enabled, with no password and no guess limit. That can lead to full site takeover.
Is Advanced IP Blocker safe to use?
Versions up to and including 8.13.13 are not safe because of the critical flaw in CVE-2026-104732. Update to the latest version and check the changelog for the login fix. No plugin is ever guaranteed bug-free, so keep auto-updates on and review your admin users regularly.
How do I fix a WordPress authentication bypass?
Update the affected plugin first, or deactivate it (or delete it if you can) when you cannot update. Then check Users for unknown administrators, rotate your secret keys (salts) to end all sessions, and change admin passwords. If you see signs of a break-in, follow a proper cleanup process before restoring anything.
Is this WordPress security plugin bug only a risk if I use 2FA?
The NVD description says the attack targets accounts that have the plugin's 2FA feature enabled. Even so, update either way. Do not depend on a narrow reading of the description when the affected range covers every version up to 8.13.13.
Does a plugin flaw mean my WordPress site was already hacked?
No. A flaw means an attack was possible, not that it happened. Because failed guesses may not show up in normal login alerts, check your administrator list, installed plugins, and host access logs to be sure.

Keep reading

See what attackers see, for free

Run the free passive check on your website. No login, no impact on your site, results in seconds.

Ready for the full manual audit? See pricing

Published by Bug Circuit. Written with AI assistance and reviewed for accuracy before publishing.