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

CVE-2025-9892

MEDIUM · 5.3 CVSS v3.1 Published 2025-10-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
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
The Restrict User Registration plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.0.1. This is due to missing or incorrect nonce validation on the update() function. This makes it possible for unauthenticated attackers to update the plugin's settings via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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

The Restrict User Registration WordPress plugin lacks proper nonce validation in its update() function, allowing unauthenticated attackers to forge administrative requests. By tricking a logged-in administrator into clicking a malicious link, an attacker can modify plugin settings without authentication.

MitigationUpdate to version 1.0.2 or later which includes proper nonce validation. Additionally, ensure administrators are educated about not clicking untrusted links.

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
None
Integrity
Low
Availability
None

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

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. Verify plugin is installed
    Check for the 'restrict-user-registration' folder in wp-content/plugins/ or search for the plugin in WordPress admin under Plugins
    Affected if The plugin is present in the WordPress installation
  2. Check installed version
    View the plugin file header (e.g., restrict-user-registration.php) for the 'Version' comment, or check the Plugins page in WordPress admin
    Affected if Version is present and less than 1.0.2 (or version cannot be determined and the plugin is installed)
  3. Verify nonce validation is missing
    Inspect the plugin update() function in the main plugin file for 'wp_verify_nonce' or 'check_admin_referer' calls; absence indicates vulnerability
    Affected if The update() function lacks proper nonce verification before processing settings changes
  4. Confirm settings can be modified
    Attempt to access the plugin settings page at Settings > Restrict User Registration (requires admin session)
    Affected if Settings page is accessible and settings can be saved without triggering nonce errors
  5. Check for recent settings changes
    Review server access logs for POST requests to admin-ajax.php or plugin settings endpoints originating from unauthenticated IPs
    Affected if Unexpected POST requests to plugin settings are logged from non-admin sessions

The environment is affected if the Restrict User Registration plugin is installed with a version earlier than 1.0.2, as the missing nonce validation allows unauthorized settings modification via forged admin requests.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to version 1.0.2 or later which includes proper nonce validation. Additionally, ensure administrators are educated about not clicking untrusted links.

Recommended fix High confidence

1.0.2 or latest available version

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the 'Restrict User Registration' plugin
  4. Check if the current version is 1.0.1 or below
  5. If vulnerable, click 'Update Now' to install the latest version
  6. Alternatively, navigate to Plugins > Add New > Upload Plugin to manually upload the updated version from wordpress.org

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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