# CVE-2026-0832: Missing authorization in New User Approve

> Unauthenticated attackers can approve or deny user accounts, retrieve sensitive user data, and force logout privileged users via missing capability checks in REST API endpoints.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Jan 2026
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-m59v-w24h-f8g6

## What is CVE-2026-0832?

CVE-2026-0832 is a high-severity missing authorization vulnerability in saadiqbal New User Approve, published on 28 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-0832?


## How do I fix CVE-2026-0832?

No fix has been published for CVE-2026-0832 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-0832 being exploited?

There is no known exploitation of CVE-2026-0832 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-0832 and fix it if it is affected.

What it is: CVE-2026-0832 is a high-severity missing authorization vulnerability in saadiqbal New User Approve, published on 28 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-0832 in the wild and no public exploit code.

Affected product: saadiqbal New User Approve. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-0832/ (Markdown: https://insights.sbomify.com/CVE-2026-0832/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-0832
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-0832
- OSV: https://osv.dev/vulnerability/CVE-2026-0832

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-0832/
Summaries are generated and may contain mistakes; the official description above is the record.