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
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.
Security readout for executives and security teams
Plain-English summary
This WordPress plugin flaw lets an unauthenticated visitor delete certain user accounts created through the User Registration & Membership plugin. It does not expose data or provide server takeover based on the cited record, but it can disrupt customer/member access and damage account integrity.
Executive priority
Prioritize for WordPress sites that rely on member accounts, paid subscriptions, or customer portals. Business impact is account disruption, support burden, and possible loss of trust rather than full system compromise based on current evidence.
Technical view
CVE-2025-3281 is a CWE-639 insecure direct object reference in create_stripe_subscription(). Versions up to and including 4.2.1 miss validation of the user-controlled member_id key, allowing unauthenticated deletion of arbitrary accounts registered through the plugin. CVSS is 5.3, network exploitable, low complexity, no privileges, no user interaction.
Likely exposure
Exposure is likely limited to WordPress sites running the User Registration & Membership plugin at version 4.2.1 or earlier, especially sites using plugin-managed registrations or membership subscription workflows.
Exploitation context
The provided sources do not show CISA KEV listing or active exploitation. The issue is remotely reachable and unauthenticated according to the CVE data, so internet-facing affected sites should treat it as actionable.
Researcher notes
The public record points to missing member_id validation in create_stripe_subscription() and a WordPress.org Trac changeset for AJAX.php. Public sources in the bundle do not confirm weaponized exploitation or provide a complete vendor advisory narrative.
Mitigation direction
Identify all WordPress sites using the affected plugin.
Check vendor or WordPress.org guidance for the fixed release.
Update the plugin to a non-affected version when available.
If unable to update, consider disabling the plugin temporarily.
Back up user data before remediation changes.
Validation and detection
Confirm installed plugin version is greater than 4.2.1 or otherwise vendor-confirmed fixed.
Review WordPress user deletion logs for unexpected account removals.
Check web logs for unusual requests to plugin membership AJAX functionality.
Verify affected membership users still exist after remediation.
Monitor vendor advisories for additional affected-version or fix details.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-639: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-639 · source CWE mapping
Authorization Bypass Through User-Controlled Key
Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.