Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N
Network-reachable WordPress endpoint, no auth or interaction, low-complexity missing-authorization flaw enabling state changes (I:H) with limited data exposure (C:L) and no DoS.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N
Lifecycle Timeline
1DescriptionCVE.org
Unauthenticated Broken Access Control in User Registration Stripe <= 1.3.12 versions.
AnalysisAI
Broken access control in the WordPress plugin User Registration Stripe (versions <= 1.3.12) allows unauthenticated remote attackers to invoke protected functionality without proper authorization checks. The flaw stems from missing capability validation (CWE-862) and carries a CVSS 3.1 score of 8.2 with high integrity impact. No public exploit identified at time of analysis, and it is not listed in CISA KEV.
Technical ContextAI
User Registration Stripe is a ThemeGrill-developed WordPress plugin (CPE: cpe:2.3:a:themegrill:user_registration_stripe) that extends the User Registration plugin family to accept Stripe-based payments during signup. The vulnerability is classified as CWE-862 (Missing Authorization), meaning at least one plugin endpoint - likely an AJAX action, REST route, or admin-post handler - fails to verify the caller's capability or nonce before executing privileged logic. In WordPress plugins, this pattern typically arises when developers register a callback via add_action('wp_ajax_nopriv_...') or a REST 'permission_callback' that returns true, exposing state-changing operations to anonymous visitors.
RemediationAI
Upstream fix available per Patchstack advisory; released patched version not independently confirmed in the provided data, so administrators should consult https://patchstack.com/database/wordpress/plugin/user-registration-stripe/vulnerability/wordpress-user-registration-stripe-plugin-1-3-12-broken-access-control-vulnerability for the exact fixed release (expected to be the next version after 1.3.12) and upgrade via the WordPress plugin dashboard. As an interim workaround, deactivate the User Registration Stripe plugin on affected sites - this will disable Stripe-based signup payments but eliminates the vulnerable code path entirely - or place the wp-admin/admin-ajax.php and /wp-json/ endpoints related to this plugin behind a WAF rule that blocks unauthenticated requests to its specific action names, accepting that custom rules may break legitimate signup flows. Audit existing users and Stripe subscription records created on or after the plugin was installed to detect possible abuse before patching.
More in User Registration Stripe
View allSame weakness CWE-862 – Missing Authorization
View allSame technique Authentication Bypass
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-37620