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

CVE-2025-14976

MEDIUM · 5.4 CVSS v3.1 Published 2026-01-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
61/100
Remediation priority · Elevated
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
The User Registration & Membership – Custom Registration Form Builder, Custom Login Form, User Profile, Content Restriction & Membership Plugin plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 4.4.8. This is due to missing or incorrect nonce validation on the 'process_row_actions' function with the 'delete' action. This makes it possible for unauthenticated attackers to delete arbitrary post 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 WordPress User Registration & Membership plugin versions up to 4.4.8 lacks proper nonce validation on the 'process_row_actions' function when handling the 'delete' action. This allows unauthenticated attackers to craft malicious links that, when clicked by an authenticated administrator, cause the plugin to delete arbitrary posts without the admin's intentional consent.

MitigationUpgrade to version 4.4.9 or later which includes proper nonce validation for the delete action. Until patched, administrators should avoid clicking untrusted links while logged in.

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
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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 User Registration plugin is installed
    Access your WordPress admin dashboard, go to Plugins > Installed Plugins, and look for 'User Registration & Membership' or 'User Registration' in the plugin list
    Affected if The plugin is not found in the installed plugins list, then this CVE does not apply
  2. Identify installed plugin version
    In the Plugins list, locate the User Registration plugin and note the version number displayed beneath the plugin name
    Affected if The installed version is 4.4.8 or earlier (any version up to and including 4.4.8)
  3. Verify admin access is available
    Confirm that administrator-level access to the WordPress dashboard exists; the attack requires a logged-in administrator to click a crafted malicious link
    Affected if Administrator accounts exist and can log in to the WordPress admin area, enabling the attack chain
  4. Check for deletable content managed by plugin
    Navigate to the User Registration plugin settings or look for post types created by the plugin (typically under Users > User Registration or a custom post type menu item)
    Affected if The plugin manages deletable content such as user registration entries, forms, or custom post types that could be targeted for deletion

Your environment is affected if the User Registration & Membership plugin version 4.4.8 or earlier is installed and administrator access to the WordPress dashboard is available, allowing the nonce validation flaw to be exploited via malicious links.

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

Upgrade to version 4.4.9 or later which includes proper nonce validation for the delete action. Until patched, administrators should avoid clicking untrusted links while logged in.

Recommended fix Moderate confidence

4.4.9 or latest available version

  1. Check the current version of the 'User Registration & Membership' plugin installed on the WordPress site
  2. Navigate to Plugins > All Plugins in the WordPress admin dashboard
  3. If the installed version is 4.4.8 or below, update to the latest available version (likely 4.4.9 or higher)

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
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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