New User ApproveWordPress extension · Wpexperts
CVE-2023-50902
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCross-Site Request Forgery (CSRF) vulnerability in WPExpertsio New User Approve.This issue affects New User Approve: from n/a through 2.5.1.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceCross-Site Request Forgery (CSRF) vulnerability in the WPExpertsio New User Approve WordPress plugin allows attackers to trick authenticated administrators into performing unauthorized actions, such as approving or rejecting user accounts, by crafting malicious requests that the victim's browser automatically submits due to missing or inadequate CSRF protections.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
New User ApproveWordPress extension
<= 2.5.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify plugin is installedNavigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'New User Approve' by WPExpertsio in the listAffected if The plugin is present and active in the WordPress installation
-
Check installed plugin versionIn the Plugins list, locate New User Approve and click on the plugin name or view details to see the version number displayedAffected if The version number displayed is 2.5.1 or lower
-
Identify state-changing actionsExamine the plugin admin pages for user approval/rejection forms (typically found under Users > New User Approve or similar admin menu items). Look for any forms that approve or reject pending user registrationsAffected if The plugin has active user approval/rejection functionality accessible to administrators
-
Verify CSRF protection presence (optional manual check)Inspect the HTML source of approval/rejection forms by right-clicking > View Page Source. Look for a hidden input field named 'wpnonce' or '_wpnonce' or similar nonce field within the form tagsAffected if No nonce field is found in the HTML source of approval/rejection forms - indicating missing CSRF protection
If the New User Approve plugin version is 2.5.1 or lower and the approval/rejection functionality exists in the admin panel, the installation is affected by this CSRF vulnerability.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement WordPress nonces on all state-changing forms and AJAX actions within the plugin, verify nonce validity server-side before processing any user approval/rejection requests, and consider adding SameSite cookie attributes and Origin/Referer header checks for additional defense-in-depth.
Fix this in New User Approve
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-50902 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-50902 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data