CVE-2025-3281: User Registration & Membership – Custom Registration Form, Login Form, and User Profile <= 4.2.1 - Insecure Direct Object Reference to Unauthenticated Limited User Deletion
First published: Tue May 06 2025(Updated: )
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.
Credit: security@wordfence.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| WordPress User Registration & Membership | <=4.2.1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://www.wordfence.com/threat-intel/vulnerabilities/id/30339ff6-b6bf-4c56-b6cd-db0b8a6ce8b6?source=cve
- https://plugins.trac.wordpress.org/browser/user-registration/tags/4.1.3/modules/membership/includes/AJAX.php#L619
- https://plugins.trac.wordpress.org/changeset/3287698/user-registration/trunk/modules/membership/includes/AJAX.php
Frequently Asked Questions
What is the severity of CVE-2025-3281?
CVE-2025-3281 is classified as a high severity vulnerability due to its potential to enable unauthorized access to user data.
How do I fix CVE-2025-3281?
To fix CVE-2025-3281, update the WordPress User Registration & Membership plugin to version 4.2.2 or later.
What types of attacks can CVE-2025-3281 allow?
CVE-2025-3281 can allow attackers to exploit Insecure Direct Object References to access or manipulate user information.
Which versions of the WordPress User Registration & Membership plugin are affected by CVE-2025-3281?
All versions of the WordPress User Registration & Membership plugin up to and including 4.2.1 are affected by CVE-2025-3281.
Is there a workaround for CVE-2025-3281?
There are no official workarounds for CVE-2025-3281, so updating the plugin is the recommended action.
- collector/mitre-cve
- source/MITRE
- agent/title
- agent/weakness
- agent/references
- agent/type
- agent/first-publish-date
- agent/description
- agent/guess-ai
- agent/software-canonical-lookup
- agent/softwarecombine
- collector/nvd-api
- source/NVD
- agent/author
- agent/last-modified-date
- agent/severity
- agent/source
- agent/tags
- agent/event
- vendor/wordpress
- canonical/wordpress user registration & membership