Is New User Approve safe to use?

Laskyr does not give safety verdicts. No known unpatched vulnerabilities in the latest version (3.3). As of 2026-11-04. 10 issues are on record for older versions; version 3.2.10 or newer fixes all of them that state a fix. Keep New User Approve on the latest version (3.3) and remove it if you do not use it.

Which versions of New User Approve are vulnerable?

Known issues on record (newest first): Information disclosure (3.1.0 up to (not including) 3.2.10, fixed in 3.2.10); Missing authorization check (3.2.8 and older, fixed in 3.2.9); Missing authorization check (3.2.3 and older, fixed in 3.2.4); Missing authorization check (3.2.0 and older, fixed in 3.2.1); Missing authorization check (3.2.2 and older, fixed in 3.2.3); Cross-site request forgery (CSRF) (3.2.3 and older, fixed in 3.2.4). The full list with sources is on this page.

What is the latest version of New User Approve?

3.3, according to wordpress.org (last updated 2026-09-30). It has 20,000+ active installs.

What should I do if my New User Approve is out of date?

Take a backup, then update it from Dashboard > Updates (or run wp plugin update new-user-approve). If you cannot update right away, deactivate it until you can. If you think the site was already attacked, run a free scan at https://laskyr.com/scan.

Plugins · new-user-approve · data as of 2026-11-04

Is New User Approve safe? Known vulnerabilities and latest version

Latest version: 3.3
Last updated: 2026-09-30
Active installs: 20,000+
Known issues on record: 10
Unpatched in latest: 0
Tested up to WP: 7.1.4

WordPress user approval plugin to moderate registrations. Approve or deny real users and prevent fake signups to control who registers on site. — by Saad Iqbal

What to do

Update to the latest version (3.3). Anything older than 3.2.10 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
If you cannot update right away, deactivate it until you can.
Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.

With WP-CLI: wp plugin get new-user-approve --field=version shows what you run; wp plugin update new-user-approve updates it.

Check your version

Known vulnerabilities

10 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.

medium 5.3 CVE-2026-83560 · published 2026-09-30

Information disclosure in New User Approve (3.1.0 up to (not including) 3.2.10)

Affected: 3.1.0 up to (not including) 3.2.10
Fixed in: 3.2.10
Access needed (per CVSS): No login needed
Range from: CVE record (the advisory publisher) · score by CISA ADP

Details from the advisory

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.

NVD CVE-2026-83560 WPScan advisory

medium 5.3 CVE-2026-28163 · published 2026-08-20

Missing authorization check in New User Approve (3.2.8 and older)

Affected: 3.2.8 and older
Fixed in: 3.2.9
Access needed (per CVSS): No login needed
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

Missing Authorization vulnerability in myCred New User Approve allows Exploiting Incorrectly Configured Access Control Security Levels. This issue affects New User Approve: from n/a through 3.2.8.

NVD CVE-2026-28163 Patchstack advisory

medium 6.5 CVE-2026-25390 · published 2026-03-25

Missing authorization check in New User Approve (3.2.3 and older)

Affected: 3.2.3 and older
Fixed in: 3.2.4
Access needed (per CVSS): Needs a low-level account (e.g. subscriber)
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

Missing Authorization vulnerability in Saad Iqbal New User Approve new-user-approve allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects New User Approve: from n/a through <= 3.2.3.

NVD CVE-2026-25390 Patchstack advisory

high 8.6 CVE-2025-69063 · published 2026-02-20

Missing authorization check in New User Approve (3.2.0 and older)

Affected: 3.2.0 and older
Fixed in: 3.2.1
Access needed (per CVSS): No login needed
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

NVD CVE-2025-69063 Patchstack advisory

high 7.3 CVE-2026-0832 · published 2026-01-28

Missing authorization check in New User Approve (3.2.2 and older)

Affected: 3.2.2 and older
Fixed in: 3.2.3 *
Access needed (per CVSS): No login needed
Range from: CVE record (the advisory publisher) · score by Wordfence

Details from the advisory

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.

NVD CVE-2026-0832 Wordfence advisory Code change (fix)Plugin source

high 7.1 CVE-2025-63030 · published 2025-12-09

Cross-site request forgery (CSRF) in New User Approve (3.2.3 and older)

Affected: 3.2.3 and older
Fixed in: 3.2.4
Access needed (per CVSS): No login needed; someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

Cross-Site Request Forgery (CSRF) vulnerability in Saad Iqbal New User Approve new-user-approve allows Cross Site Request Forgery.This issue affects New User Approve: from n/a through <= 3.2.3.

NVD CVE-2025-63030 Patchstack advisory

medium 5.3 CVE-2025-12770 · published 2025-11-19

Information disclosure in New User Approve (3.0.9 and older)

Affected: 3.0.9 and older
Fixed in: 3.1.0 *
Access needed (per CVSS): No login needed
Range from: CVE record (the advisory publisher) · score by Wordfence

Details from the advisory

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.

NVD CVE-2025-12770 Wordfence advisory Plugin source

medium 5.4 CVE-2024-54323 · published 2024-12-13

Missing authorization check in New User Approve (2.6.2 and older)

Affected: 2.6.2 and older
Fixed in: 2.6.4
Access needed (per CVSS): Needs a low-level account (e.g. subscriber)
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

NVD CVE-2024-54323 Patchstack advisory

high 8.8 CVE-2023-50902 · published 2023-12-29

Cross-site request forgery (CSRF) in New User Approve (2.5.1 and older)

Affected: 2.5.1 and older
Fixed in: 2.5.2
Access needed (per CVSS): No login needed; someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by NVD

Details from the advisory

Cross-Site Request Forgery (CSRF) vulnerability in WPExpertsio New User Approve.This issue affects New User Approve: from n/a through 2.5.1.

NVD CVE-2023-50902 Patchstack advisory

medium 4.3 CVE-2022-1625 · published 2022-06-27

Cross-site request forgery (CSRF) in New User Approve (older than 2.4)

Affected: older than 2.4
Fixed in: 2.4
Access needed (per CVSS): No login needed; someone on the site has to click a link or open a page
Range from: NVD analysis · score by NVD

Details from the advisory

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.

NVD CVE-2022-1625 WPScan advisory

Recent activity

2026-09-30 — latest release on wordpress.org (3.3).
2026-09-30 — Information disclosure disclosed (CVE-2026-83560), fixed in 3.2.10.
2026-08-20 — Missing authorization check disclosed (CVE-2026-28163), fixed in 3.2.9.
2026-03-25 — Missing authorization check disclosed (CVE-2026-25390), fixed in 3.2.4.

Free. We check the CVE feeds every day and email you only when a new issue for New User Approve (new-user-approve) is published or a fix ships. Unsubscribe in one click.

Browse vulnerabilities

Types found in this plugin: Missing authorization (5) · Cross-site request forgery (CSRF) (3) · Sensitive data exposure (2)

Where this data comes from

Version, last update, installs: wordpress.org/plugins/new-user-approve (Plugins API), fetched 2026-11-04.
Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.

Badge for your site or docs (states facts with a date, not a verdict):

<a href="https://laskyr.com/plugins/new-user-approve"><img src="https://laskyr.com/plugins/new-user-approve/badge.svg" alt="New User Approve vulnerability status"></a>

← Check another plugin · Free hacked-site scan

Is New User Approve safe? Known vulnerabilities and latest version

No known unpatched vulnerabilities in the latest version (3.3)

What to do

Check your version

Known vulnerabilities

Information disclosure in New User Approve (3.1.0 up to (not including) 3.2.10)

Missing authorization check in New User Approve (3.2.8 and older)

Missing authorization check in New User Approve (3.2.3 and older)

Missing authorization check in New User Approve (3.2.0 and older)

Missing authorization check in New User Approve (3.2.2 and older)

Cross-site request forgery (CSRF) in New User Approve (3.2.3 and older)

Information disclosure in New User Approve (3.0.9 and older)

Missing authorization check in New User Approve (2.6.2 and older)

Cross-site request forgery (CSRF) in New User Approve (2.5.1 and older)

Cross-site request forgery (CSRF) in New User Approve (older than 2.4)

Recent activity

Get an email when New User Approve has a new vulnerability

Browse vulnerabilities

Where this data comes from