CVE-2026-18960

Block User Account <= 2.0.0 - Missing Authorization to Authenticated (Subscriber+) Account Block Bypass

2026-08-06 00:00
Farid Narimanov

Strategic Overview

Status
Patched in 2.0.1
Affected Plugin
Block User Account
Affected Version
<= 2.0.0
CVSS
4.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2026-18960
View all Block User Account vulnerabilities

At a glance

CVE-2026-18960 is a medium-severity Missing Authorization vulnerability in the Block User Account WordPress plugin, affecting versions <= 2.0.0. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 2.0.1; sites on affected versions should update now. Disclosed August 2026, reported by Farid Narimanov.

Vulnerability Overview

The Block User Account plugin for WordPress is vulnerable to unauthorized access in versions up to, and including, 2.0.0. This is due to a missing capability check on a function. This makes it possible for authenticated attackers, with subscriber-level access and above, to perform an unauthorized action.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.

CWE-862: Missing Authorization

Reaching this weakness in Block User Account <= 2.0.0 takes an account at Subscriber level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Block User Account the fix is 2.0.1: builds <= 2.0.0 are affected, anything from 2.0.1 onward is not.

Remediation

Update to version 2.0.1, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Block User Account 2.0.1 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C