CVE-2025-12770

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

2025-11-18 15:26
Powpy

Strategic Overview

Status
Patched in 3.1.0
Affected Plugin
New User Approve
Affected Version
<= 3.0.9
CVSS
5.3Medium
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE-2025-12770
View all New User Approve vulnerabilities

At a glance

CVE-2025-12770 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the New User Approve WordPress plugin, affecting versions <= 3.0.9. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.1.0; sites on affected versions should update now. Disclosed November 2025, reported by Powpy.

Vulnerability Overview

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.

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-200: Exposure of Sensitive Information to an Unauthorized Actor

Reaching this weakness in New User Approve <= 3.0.9 takes no account at all. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.

The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For New User Approve the fix is 3.1.0: builds <= 3.0.9 are affected, anything from 3.1.0 onward is not.

Remediation

Update to version 3.1.0, 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.1.0 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-12770https://www.wordfence.com/threat-intel/vulnerabilities/id/3f1cf77a-64b4-405b-adcb-ef16d9e82ab2https://nvd.nist.gov/vuln/detail/CVE-2025-12770

Related records

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