Radar sectionsDatabase
Check my site
WordPress plugin

New User Approve <= 3.0.9 — Unauthenticated Sensitive Information Disclosure via Type Juggling

CVE-2025-12770Published · Updated

Action summary

Affected: ≤3.0.9Update to 3.1.0 or newer

All remediation steps
Severity
Medium5.3
CVSS
5.3
CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
What does this vector mean?
AV:N Attack vector
Network
AC:L Attack complexity
Low
PR:N Privileges required
None
UI:N User interaction
None
S:U Scope
Unchanged
C:L Confidentiality
Low
I:N Integrity
None
A:N Availability
None
Weakness
CWE-200 Information Exposure
Required access
No account needed
Exploit prediction (EPSS)
No score
CISA KEV
Not listed

Am I affected?

New User Approve new-user-approve

  1. Affected≤ 3.0.9
  2. Patched in3.1.0

Update to 3.1.0 or newer.

You are affected if you run ≤ 3.0.9. Version 3.1.0 and later are not affected by this issue.

  • Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under New User Approve.
  • No admin access? Run a passive check of your site. It reads public files only.
  • No account is needed to exploit this. Treat any exposed site on an affected version as at risk.

What to do

  1. Update to version 3.1.0, or a newer patched version
  2. Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
  3. Watch New User Approve to get an email when the next vulnerability is published.

Advisory

Source description from Wordfence Intelligence, credited to Powpy.

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.

Exploits & references

Proof-of-concept & detection

No public proof-of-concept or detection template is known for this vulnerability.

Advisories & patches

More in New User Approve

All 13
More vulnerabilities in New User Approve
SeverityVulnerabilityCVEPublished
Medium5.33.2.9 - Unauthenticated Information Exposure
3.1.0 – 3.2.9Update to 3.2.10
CVE-2026-83560
Medium5.3Missing Authorization
≤3.2.8Update to 3.2.9
CVE-2026-28163
Medium4.3Missing Authorization
≤3.2.3Update to 3.2.4
CVE-2026-25390
Medium5.3Missing Authorization
≤3.2.0Update to 3.2.1
CVE-2025-69063
High7.3Missing Authorization to Unauthenticated Arbitrary User Approval, Denial, and Information Disclosure
≤3.2.2Update to 3.2.3
CVE-2026-0832

Same weakness (Information Exposure)

All Information Exposure
Other Information Exposure vulnerabilities
SeverityVulnerabilityCVEPublished
High7.2Unauthenticated Stored Cross-Site Scripting via Comment User-Agent HeaderCVE-2026-120688
Critical9.8Unauthenticated Arbitrary File Upload via File Upload via Public Form SubmissionCVE-2026-125055
Critical9.8Unauthenticated PHP Object Injection to Remote Code Execution via 'form' ParameterCVE-2026-119077
Medium5.3Unauthenticated Sensitive Information Exposure in 'search' Parameter
Customer Reviews for WooCommerce≤5.127.0Update to 5.128.0
CVE-2026-121518

Timeline

  1. CVE published

    Severity medium, CVSS 5.3

  2. Record last updated

Sources & licenses

Wordfence record
Vulnerability data
Wordfence Intelligence. [object Object] Licensed under the CC BY-SA 4.0.
CVE® identifiers
[object Object]. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
CVSS / CWE
National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
VulnCrest content
Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.

How we use these sources

Search VulnCrest Radar

Are you sure?