Skip to main content
VulnerabilityPublished Updated

CVE-2026-18960: Block User Account (WordPress plugin) · Improper Authentication

Affects Block User Account (WordPress plugin)Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.4 Medium : upgrade to 2.0.1 when convenient.

Data as of 8 Nov 2026, 23:24 UTC

CVSS 3.1 base score
5.4Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.0.1
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 8 Nov 2026.

What to do

Upgrade Block User Account (WordPress plugin) to 2.0.1.

Affected software

ProductAffectedFixed in
Block User AccountAffected
  • <2.0.1
Fixed in
  • 2.0.1

AI-suggested

A fix is available in Block User Account plugin version 2.0.1. Users should upgrade to version 2.0.1 or later to ensure that account blocks are enforced on all authentication paths, including application passwords. Patch status is not explicitly confirmed in the vendor advisory, but the version 2.0.1 release implies remediation. Until updated, administrators should consider revoking all application passwords for blocked users as a temporary mitigation.

Description

The Block User Account WordPress plugin before 2.0.1 does not enforce its account block on every authentication path, allowing a blocked user who holds an application password created before the block to retain their full role-level read and write access through the REST API.

References

Community reviews

Loading reviews…