HomeWordPress vulnerabilitiesNew User Approve
New User Approve vulnerabilities
New User Approve has 4 known vulnerabilities in this database. The most recent published record is dated 30 Sep 2026.
- Known vulnerabilities
- 4
- Active installs
- 20,000+
- Latest version
- 3.3
- Last updated
- 30 Sep 2026
- Most recent
- 30 Sep 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Sensitive data exposure CVE-2026-83560 | Medium 5.3 | Before 3.2.10 | Fixed in 3.2.10 | 7 d ago |
| Broken access control CVE-2026-0832 | High 7.3 | Up to 3.2.2 | Fixed in a later version (latest 3.3) | 28 Jan 2026 |
| Broken access control CVE-2025-12770 | Medium 5.3 | Up to 3.0.9 | Fixed in a later version (latest 3.3) | 19 Nov 2025 |
| Cross-site request forgery (CSRF) CVE-2022-1625 | Medium 4.3 | Before 2.4 | Fixed in 2.4 | 27 Jun 2022 |
Read the published descriptions
- CVE-2026-83560, 30 Sep 2026
- The New User Approve WordPress plugin before 3.2.10 does not properly verify authentication on a set of integration REST API routes when the integration is unconfigured, allowing unauthenticated attackers to retrieve personal data (id, username, email address and registration date) of registered users. CVE record
- CVE-2026-0832, 28 Jan 2026
- The New User Approve plugin for WordPress is vulnerable to unauthorized access of data and modification of data due to a missing capability check on multiple REST API endpoints in all versions up to, and including, 3.2.2. This makes it possible for unauthenticated attackers to approve or deny user accounts, retrieve sensitive user information including emails and roles, and force logout of privileged users. CVE record
- CVE-2025-12770, 19 Nov 2025
- 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. CVE record
- CVE-2022-1625, 27 Jun 2022
- The New User Approve WordPress plugin before 2.4 does not have CSRF check in place when updating its settings and adding invitation codes, which could allow attackers to add invitation codes (for bypassing the provided restrictions) and to change plugin settings by tricking admin users into visiting specially crafted websites. CVE record
What to do if you run New User Approve
If you run New User Approve, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new New User Approve vulnerabilities
Free. We email you when a new vulnerability is published for New User Approve, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.