dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-69063

HIGH · 8.6 CVSS v3.1 Published 2026-02-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
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.0.

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 · moderate confidence

This is a missing authorization vulnerability in the New User Approve WordPress plugin. The plugin fails to properly enforce authorization checks, allowing attackers to exploit incorrectly configured access control security levels to perform actions they should not have permission to perform. The vulnerability affects all versions up to and including 3.2.0.

MitigationImplement proper role-based capability checks and authorization validation on all sensitive endpoints and actions within the plugin to ensure users can only access functionality permitted by their assigned roles.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm plugin installation and version
    In WordPress admin, go to Plugins > Installed Plugins and locate 'New User Approve'. Check the version listed. Alternatively, inspect the plugin main file (new-user-approve/new-user-approve.php) and read the Version header comment.
    Affected if The plugin is installed and its version is 3.2.0 or lower (any version up to and including 3.2.0).
  2. Identify enabled user roles and capabilities
    Navigate to Users > Roles in WordPress admin, or use a role management plugin or wp-cli command 'wp role list' to enumerate active roles. Review which roles have 'manage_options', 'approve_users', or custom capabilities added by the plugin.
    Affected if Non-administrator roles (editors, authors, contributors, or custom roles) have been granted elevated capabilities beyond what they should normally possess, or the plugin has added capabilities that allow bypassing authorization.
  3. Inspect plugin capability configuration
    Check the plugin settings at Settings > New User Approve (or similar admin page). Look for any options controlling which user roles can approve, reject, or manage other users. Inspect the plugin source code for add_cap() calls or role modification functions.
    Affected if The plugin assigns elevated capabilities (such as user management or approval rights) to roles that should not possess them, or fails to check capabilities before performing sensitive actions.
  4. Verify sensitive admin actions are capability-protected
    Review the plugin PHP files for functions handling user approval, rejection, or admin actions. Search for current_user_can() calls and verify each sensitive operation has a proper capability check before execution.
    Affected if Sensitive functions (user approval, role changes, data export) are missing current_user_can() checks or use weak/incorrect capability verification, allowing unauthenticated or underprivileged users to trigger them.

You are affected if the New User Approve plugin version is 3.2.0 or lower AND your site has user roles configured with elevated capabilities or the plugin fails to enforce capability checks on sensitive actions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper role-based capability checks and authorization validation on all sensitive endpoints and actions within the plugin to ensure users can only access functionality permitted by their assigned roles.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-69063 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-69063 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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