# CVE-2025-12770: New User Approve <= 3.0.9 - Unauthenticated Sensitive Information Disclosure via Type Juggling

> Unauthenticated attackers can retrieve user PII via type juggling in the Zapier API if the key is unconfigured.

- **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:** 19 Nov 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-xhjc-3h89-4qhf

## What is CVE-2025-12770?

CVE-2025-12770 is a medium-severity vulnerability in saadiqbal New User Approve, published on 19 Nov 2025. 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 data disclosure in all versions up to, and including, 3.0.9 due to insufficient API key validation using loose equality comparison. This makes it possible for unauthenticated attackers to retrieve personally identifiable information (PII), including usernames and email addresses of users with various approval statuses via the Zapier REST API endpoints, by exploiting PHP type juggling with the api_key parameter set to "0" on sites where the Zapier API key has not been configured.

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

## Which versions are affected by CVE-2025-12770?


## How do I fix CVE-2025-12770?

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

## Is CVE-2025-12770 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-12770 and fix it if it is affected.

What it is: CVE-2025-12770 is a medium-severity vulnerability in saadiqbal New User Approve, published on 19 Nov 2025. 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-2025-12770 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-2025-12770/ (Markdown: https://insights.sbomify.com/CVE-2025-12770/index.md)
```

## Sources

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

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