New User Approve Plugin up to 3.0.9 on WordPress REST API Endpoint api_key information disclosure

Summaryinfo

A vulnerability was found in New User Approve Plugin up to 3.0.9 on WordPress. It has been classified as problematic. Affected by this issue is some unknown functionality of the component REST API Endpoint. Performing a manipulation of the argument api_key results in information disclosure. This vulnerability was named CVE-2025-12770. The attack may be initiated remotely. There is no available exploit.

Detailsinfo

A vulnerability classified as problematic has been found in New User Approve Plugin up to 3.0.9 on WordPress. This affects an unknown code block of the component REST API Endpoint. The manipulation of the argument api_key with an unknown input leads to a information disclosure vulnerability. CWE is classifying the issue as CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. This is going to have an impact on confidentiality. The summary by CVE is:

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.

It is possible to read the advisory at wordfence.com. This vulnerability is uniquely identified as CVE-2025-12770. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1592 according to MITRE ATT&CK.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the databases at CNNVD (CNNVD-202511-2271) and EUVD (EUVD-2025-198127). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

• WordPress Plugin

Name

• New User Approve Plugin

Version

• 3.0.0
• 3.0.1
• 3.0.2
• 3.0.3
• 3.0.4
• 3.0.5
• 3.0.6
• 3.0.7
• 3.0.8
• 3.0.9

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion