dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2025-63030

HIGH · 7.1 CVSS v3.1 Published 2025-12-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges

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
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.

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 confidence

Cross-Site Request Forgery (CSRF) vulnerability in the New User Approve WordPress plugin allows attackers to trick authenticated administrators into performing unwanted actions like approving or denying user registration requests by forcing their browser to send malicious requests.

MitigationImplement anti-CSRF tokens (WordPress nonces) on all form submissions and state-changing actions, and verify request origin via referer header checks or SameSite cookie attributes.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/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 checks

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

  1. Confirm New User Approve plugin is installed
    Navigate to WordPress admin dashboard > Plugins and verify the 'New User Approve' plugin is installed and active
    Affected if Plugin is installed and active with no CSRF protection in place
  2. Identify installed plugin version
    In Plugins list, click 'View details' on New User Approve or check the plugin header in wp-content/plugins/new-user-approve/new-user-approve.php for the Version comment
    Affected if Version is earlier than the patched release (compare to changelog or WordPress plugin repository for fixed version number)
  3. Inspect plugin forms for nonce fields
    Using browser developer tools or by examining plugin source code in new-user-approve/templates/, locate forms that handle user approval/denial actions and verify wp_nonce_field() calls are present
    Affected if Approval/denial forms lack WordPress nonce tokens (wp_nonce_field) or referer checks (check_admin_referer)
  4. Check admin action handlers for CSRF validation
    Examine the plugin PHP handlers that process approval/denial requests (typically in main plugin file) for nonce verification using wp_verify_nonce or check_admin_referer before processing state changes
    Affected if Action handlers process requests without verifying nonce tokens or request origin

Environment is affected if New User Approve plugin is installed, lacks the patched version, and does not implement WordPress nonce validation on user approval/denial form submissions.

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 anti-CSRF tokens (WordPress nonces) on all form submissions and state-changing actions, and verify request origin via referer header checks or SameSite cookie attributes.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-63030 — 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-63030 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