Is Advanced IP Blocker safe to use?

Laskyr does not give safety verdicts. No known unpatched vulnerabilities in the latest version (8.13.23). As of 2026-11-04. 2 issues are on record for older versions; version 8.13.14 or newer fixes all of them that state a fix. Keep Advanced IP Blocker on the latest version (8.13.23) and remove it if you do not use it.

Which versions of Advanced IP Blocker are vulnerable?

Known issues on record (newest first): Authentication bypass (8.13.13 and older, fixed in 8.13.14); Cross-site scripting (XSS) (8.10.7 and older, fixed in 8.10.8). The full list with sources is on this page.

What is the latest version of Advanced IP Blocker?

8.13.23, according to wordpress.org (last updated 2026-10-31). It has 3,000+ active installs.

What should I do if my Advanced IP Blocker is out of date?

Take a backup, then update it from Dashboard > Updates (or run wp plugin update advanced-ip-blocker). If you cannot update right away, deactivate it until you can. If you think the site was already attacked, run a free scan at https://laskyr.com/scan.

Plugins · advanced-ip-blocker · data as of 2026-11-04

Is Advanced IP Blocker safe? Known vulnerabilities and latest version

Latest version: 8.13.23
Last updated: 2026-10-31
Active installs: 3,000+
Known issues on record: 2
Unpatched in latest: 0
Tested up to WP: 7.1.4 · PHP 8.1+

A complete WordPress security firewall: blocks IPs, bots, countries & ASN. Includes an intelligent WAF, Threat Scoring, Geo-Challenge, and 2FA. — by IniLerm

What to do

Update to the latest version (8.13.23). Anything older than 8.13.14 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
If you cannot update right away, deactivate it until you can.
Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.

With WP-CLI: wp plugin get advanced-ip-blocker --field=version shows what you run; wp plugin update advanced-ip-blocker updates it.

Check your version

Known vulnerabilities

2 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.

critical 9.8 CVE-2026-104732 · published 2026-10-10

Authentication bypass in Advanced IP Blocker (8.13.13 and older)

Affected: 8.13.13 and older
Fixed in: 8.13.14 *
Access needed (per CVSS): No login needed
Range from: CVE record (the advisory publisher) · score by Wordfence

Details from the advisory

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.

NVD CVE-2026-104732 Wordfence advisory Code change (fix)Plugin source

high 7.1 CVE-2026-42739 · published 2026-05-27

Cross-site scripting (XSS) in Advanced IP Blocker (8.10.7 and older)

Affected: 8.10.7 and older
Fixed in: 8.10.8
Access needed (per CVSS): No login needed; someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in IniLerm Advanced IP Blocker advanced-ip-blocker allows DOM-Based XSS.This issue affects Advanced IP Blocker: from n/a through <= 8.10.7.

NVD CVE-2026-42739 Patchstack advisory

Recent activity

2026-10-31 — latest release on wordpress.org (8.13.23).
2026-10-10 — Authentication bypass disclosed (CVE-2026-104732), fixed in 8.13.14.
2026-05-27 — Cross-site scripting (XSS) disclosed (CVE-2026-42739), fixed in 8.10.8.

Free. We check the CVE feeds every day and email you only when a new issue for Advanced IP Blocker (advanced-ip-blocker) is published or a fix ships. Unsubscribe in one click.

Browse vulnerabilities

Types found in this plugin: Authentication bypass (1) · Cross-site scripting (XSS) (1)

Where this data comes from

Version, last update, installs: wordpress.org/plugins/advanced-ip-blocker (Plugins API), fetched 2026-11-04.
Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.

Badge for your site or docs (states facts with a date, not a verdict):

<a href="https://laskyr.com/plugins/advanced-ip-blocker"><img src="https://laskyr.com/plugins/advanced-ip-blocker/badge.svg" alt="Advanced IP Blocker vulnerability status"></a>

← Check another plugin · Free hacked-site scan