# CVE-2026-83560: New User Approve 3.1.0 - 3.2.9 - Unauthenticated PII Disclosure via Zapier API Key Bypass

> Unauthenticated attackers can retrieve personal user data via REST API routes in the New User Approve WordPress plugin.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Sep 2026
- **Updated:** 30 Sep 2026
- **Also known as:** GHSA-h3cp-h7xg-mwjx

## What is CVE-2026-83560?

CVE-2026-83560 is a medium-severity vulnerability in Unknown New User Approve, published on 30 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The New User Approve WordPress plugin before 3.2.10 does not properly verify authentication on a set of integration REST API routes when the integration is unconfigured, allowing unauthenticated attackers to retrieve personal data (id, username, email address and registration date) of registered users.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2026-83560 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-83560 is a medium-severity vulnerability in Unknown New User Approve, published on 30 Sep 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-83560 in the wild and no public exploit code.

Affected product: Unknown 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-83560/ (Markdown: https://insights.sbomify.com/CVE-2026-83560/index.md)
```

## Sources

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

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