CVE-2026-0832

New User Approve <= 3.2.2 - Missing Authorization to Unauthenticated Arbitrary User Approval, Denial, and Information Disclosure

2026-01-27 17:49
Deadbee

Strategic Overview

Status
Patched in 3.2.3
Affected Plugin
New User Approve
Affected Version
<= 3.2.2
CVSS
7.3High
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2026-0832
View all New User Approve vulnerabilities

At a glance

CVE-2026-0832 is a high-severity Missing Authorization vulnerability in the New User Approve WordPress plugin, affecting versions <= 3.2.2. It carries a CVSS score of 7.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.2.3; sites on affected versions should update now. Disclosed January 2026, reported by Deadbee.

Vulnerability Overview

The New User Approve plugin for WordPress is vulnerable to unauthorized access of data and modification of data due to a missing capability check on multiple REST API endpoints in all versions up to, and including, 3.2.2. This makes it possible for unauthenticated attackers to approve or deny user accounts, retrieve sensitive user information including emails and roles, and force logout of privileged users.

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 privileges on the target site, and no interaction from a victim user.

CWE-862: Missing Authorization

Reaching this weakness in New User Approve <= 3.2.2 takes no account at all. 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 New User Approve the fix is 3.2.3: builds <= 3.2.2 are affected, anything from 3.2.3 onward is not.

Remediation

Update to version 3.2.3, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: New User Approve 3.2.3 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-0832https://www.wordfence.com/threat-intel/vulnerabilities/id/f86a69ab-2fc5-4c84-872b-929dbec429cdhttps://nvd.nist.gov/vuln/detail/CVE-2026-0832

Related records

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