CVE-2026-88827

Disable Users <= 1.0.5 - Disabled Account Authorization Bypass

2026-10-09 00:00

Strategic Overview

Status: Unpatched
Affected Plugin: Disable Users
Affected Version: <= 1.0.5
CVSS: 4.3Medium
Weakness type: CWE-287 · Improper Authentication
CVE: CVE-2026-88827

At a glance

CVE-2026-88827 is a medium-severity Improper Authentication vulnerability in the Disable Users WordPress plugin, affecting versions <= 1.0.5. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). No fixed release has been reported yet; treat installations running this software as exposed. Disclosed October 2026, reported by Naoki Kawahigashi.

Vulnerability Overview

The Disable Users plugin for WordPress is vulnerable to protection mechanism failure in all versions up to, and including, 1.0.5. This is due to the plugin not properly restricting XMLRPC and Application Passwords for disabled accounts. This makes it possible for authenticated attackers, with subscriber-level access and above, to bypass disabled account restrictions.

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-287: Improper Authentication

Reaching this weakness in Disable Users <= 1.0.5 takes a caller who can reach the endpoint. Improper authentication means the mechanism that proves who a caller is can be satisfied without the secret it was supposed to require.

An attacker authenticates as another user — administrators included — without ever knowing a password, so password policies and login rate limits never come into play. No fixed build of this plugin is recorded for Disable Users yet, so installs running <= 1.0.5 stay exposed until the vendor ships one.

Remediation

No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.

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. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.

Login Security
Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-88827 https://www.wordfence.com/threat-intel/vulnerabilities/id/9ab5890f-2657-4a35-9dfd-a4b9f7ad28d3 https://nvd.nist.gov/vuln/detail/CVE-2026-88827

CVSS Vector

4.3

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

Base

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredLow
User InteractionNone
ScopeUnchanged
ConfidentialityNone
IntegrityLow
AvailabilityNone

This record contains material that is subject to copyright

CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.

https://www.cve.org/Legal/TermsOfUse

Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.

https://www.wordfence.com/wordfence-intelligence-terms-and-conditions/