dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2025-3281

MEDIUM · 5.3 CVSS v3.1 Published 2025-05-06
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 User Registration & Membership – Custom Registration Form, Login Form, and User Profile plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 4.2.1 via the create_stripe_subscription() function, due to missing validation on the 'member_id' user controlled key. This makes it possible for unauthenticated attackers to delete arbitrary user accounts that have registered through the plugin.

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 has an IDOR vulnerability in the create_stripe_subscription() function. The plugin fails to validate the user-controlled 'member_id' parameter, allowing unauthenticated attackers to delete arbitrary user accounts that registered through the plugin.

MitigationUpdate to a patched version when available. If no patch exists, disable or remove the plugin until a fix is released. Implement web application firewall rules to block or sanitize the member_id parameter as a temporary mitigation.

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 WordPress User Registration & Membership plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'user-registration' or similar, or log into WordPress admin and navigate to Plugins > Installed Plugins to confirm the plugin is present.
    Affected if The plugin is installed and active on the WordPress site.
  2. Identify the installed plugin version
    If the plugin is installed, open the main plugin file (typically user-registration.php) and locate the version in the plugin header comment, or check the version column in WordPress admin under Plugins > Installed Plugins.
    Affected if The installed version has not yet received a patch for this IDOR vulnerability.
  3. Confirm Stripe subscription feature is enabled
    Navigate to WordPress admin > User Registration > Settings > Payment > Stripe, or inspect the plugin settings to determine if Stripe subscription functionality is configured and active.
    Affected if Stripe subscriptions are enabled and the create_stripe_subscription() function is accessible.
  4. Review server access logs for member_id parameter manipulation
    Search web server access logs (Apache, Nginx) for incoming requests to any Stripe-related endpoint containing the 'member_id' parameter, especially unusual or repeated DELETE operations targeting arbitrary user IDs.
    Affected if Requests with manipulated member_id parameters are present, indicating exploitation attempts.
  5. Check for unexpected user account deletions
    Query the WordPress database (wp_users and wp_usermeta tables) for user accounts that were recently deleted, or review the WordPress admin Users list for gaps in user IDs or unexpected account removals.
    Affected if User accounts registered through the plugin have been deleted without admin action.

A site is affected if it has the User Registration & Membership plugin installed with Stripe subscriptions enabled and evidence of unauthorized user deletions or exploitation attempts in logs.

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 a patched version when available. If no patch exists, disable or remove the plugin until a fix is released. Implement web application firewall rules to block or sanitize the member_id parameter as a temporary mitigation.

Recommended fix Moderate confidence

Latest version after 4.2.1 (check wordpress.org for current stable release)

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate the 'User Registration & Membership' plugin
  4. Check if the current version is 4.2.1 or below
  5. If vulnerable, click 'Update Now' to install the latest version
  6. Alternatively, download the latest version from wordpress.org/plugins/user-registration and upload via Plugins > Add New > Upload Plugin
  7. After update, verify the version number reflects the patched release

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-3281 — 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-3281 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