CVE-2025-12770: CWE-200 Exposure of Sensitive Information to an Unauthorized Actor in saadiqbal New User Approve
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.
AI Analysis
Technical Summary
CVE-2025-12770 is a vulnerability in the New User Approve WordPress plugin (up to version 3.0.9) caused by improper API key validation using loose equality comparison. This flaw allows unauthenticated attackers to bypass authentication checks by exploiting PHP type juggling with the api_key parameter set to "0". As a result, attackers can access the Zapier REST API endpoints and retrieve personally identifiable information, including usernames and email addresses of users with various approval statuses. The vulnerability is classified under CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) and has a CVSS 3.1 base score of 5.3 (medium severity). There is no indication of known exploits in the wild or an available patch at this time.
Potential Impact
The vulnerability allows unauthenticated attackers to access sensitive user information such as usernames and email addresses via the Zapier REST API endpoints. This exposure of personally identifiable information could lead to privacy violations and potential further targeted attacks. There is no impact on integrity or availability reported.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is released, administrators should consider disabling the Zapier API integration or ensuring that the Zapier API key is properly configured to prevent exploitation. Monitoring for unauthorized access attempts to the API endpoints is also advisable.
CVE-2025-12770: CWE-200 Exposure of Sensitive Information to an Unauthorized Actor in saadiqbal New User Approve
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.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2025-12770 is a vulnerability in the New User Approve WordPress plugin (up to version 3.0.9) caused by improper API key validation using loose equality comparison. This flaw allows unauthenticated attackers to bypass authentication checks by exploiting PHP type juggling with the api_key parameter set to "0". As a result, attackers can access the Zapier REST API endpoints and retrieve personally identifiable information, including usernames and email addresses of users with various approval statuses. The vulnerability is classified under CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) and has a CVSS 3.1 base score of 5.3 (medium severity). There is no indication of known exploits in the wild or an available patch at this time.
Potential Impact
The vulnerability allows unauthenticated attackers to access sensitive user information such as usernames and email addresses via the Zapier REST API endpoints. This exposure of personally identifiable information could lead to privacy violations and potential further targeted attacks. There is no impact on integrity or availability reported.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is released, administrators should consider disabling the Zapier API integration or ensuring that the Zapier API key is properly configured to prevent exploitation. Monitoring for unauthorized access attempts to the API endpoints is also advisable.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Wordfence
- Date Reserved
- 2025-11-05T19:45:17.059Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 691d3cbbc00dea8b9c9becbb
Added to database: 11/19/2025, 3:42:51 AM
Last enriched: 4/9/2026, 4:19:37 PM
Last updated: 5/10/2026, 8:40:23 AM
Views: 106
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.