Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify store with role-selection enabled
-
DeliverySend crafted /wc/store/v1/checkout request
-
ExploitSet afreg_select_user_role to administrator
-
ExecutionPlugin persists role in order meta
-
Persistthankyou hook calls add_role() unvalidated
-
ImpactAttacker account becomes Administrator
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V8 - Authorization Least privilege enforcement
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | The exploit requires the plugin's 'User Role Selection' setting to be enabled (a non-default configuration); without it the vulnerable role-assignment path is not exercised. Given that setting, no authentication is required (PR:N) and no user interaction beyond the attacker completing their own checkout: the attacker sends a modified JSON body to the unauthenticated /wc/store/v1/checkout Store API endpoint with afreg_select_user_role set to 'administrator' (or any role slug), and the plugin persists and later applies it via WP_User::add_role() with no allow-list validation. Limiting factors: the target must run Custom User Registration Fields for WooCommerce ≤ 2.2.3 with the role-selection feature active, and the account-creation-during-checkout flow must be available. |
| Impact | The supplied CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, base 9.8) reflects remote, unauthenticated, low-complexity exploitation yielding full compromise, which is consistent with the described attack. The one material caveat is that exploitation depends on the non-default 'User Role Selection' setting being enabled - a deployment condition the raw CVSS score does not capture, so real-world exposure is narrower than 9.8 alone implies. No EPSS score, KEV entry, POC, or SSVC data was provided; therefore there is no evidence of active exploitation and no public exploit identified at time of analysis. The signal quality is otherwise strong: the description names exact functions, the parameter, and the vulnerable code path, and the report comes from Wordfence, a credible source. Net: a genuinely high-priority issue for any site running this plugin with the role-selection feature on, but the config prerequisite means it is not universally exploitable across all installs. |
| Exploit ScenarioDerived | An attacker browses to a store running the vulnerable plugin with 'User Role Selection' enabled, initiates a checkout that creates an account, and intercepts or crafts the /wc/store/v1/checkout Store API request to set afreg_select_user_role to 'administrator'. Once the order reaches the thank-you page, the plugin assigns the administrator role to the attacker's new account, giving full control of the site. No public exploit code was identified, but the attack requires only a standard HTTP client and no authentication. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 29, 2026
Privilege escalation to Administrator in the Addify Custom User Registration Fields for WooCommerce plugin (versions ≤ 2.2.3) lets unauthenticated attackers gain admin rights by supplying an arbitrary role slug during WooCommerce checkout. The plugin trusts an attacker-controlled afreg_select_user_role value from the unauthenticated Store API /wc/store/v1/checkout request and passes it straight to WP_User::add_role() without validating it against the admin-configured allowed role list. No public exploit identified at time of analysis, and exploitation requires the plugin's 'User Role Selection' feature to be enabled.
RemediationAI
No vendor-released patch version was identified in the available data, so update to any release newer than 2.2.3 once the vendor publishes one and monitor the Wordfence advisory (https://www.wordfence.com/threat-intel/vulnerabilities/id/715723e7-5820-4a64-848f-f89b5b73a681?source=cve) and the product page (https://woocommerce.com/products/custom-user-registration-fields-for-woocommerce/) for a fix. As an immediate compensating control, disable the plugin's 'User Role Selection' setting, which removes the exploit prerequisite entirely at the cost of losing the role-selection-at-registration feature; if that feature is not needed, deactivating the plugin eliminates the risk. Additionally, audit existing users for unexpected administrator or elevated-role accounts created via checkout, and consider a WAF rule to block or strip the afreg_select_user_role parameter from /wc/store/v1/checkout requests, noting this may interfere with legitimate role selection if the feature is in use.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The affected component is a WordPress registration add-on for WooCommerce (CPE cpe:2.3:a:addify:custom_user_registration_fields_for_woocommerce). The flaw is a CWE-269 (Improper Privilege Management) issue: during the block-based checkout flow, af_reg_checkout_data_to_order_meta_data_block() captures the afreg_select_user_role field from the JSON body of the unauthenticated WooCommerce Store REST API endpoint (/wc/store/v1/checkout) and persists it into order meta. Later, on the woocommerce_thankyou hook, af_reg_custom_order_processing_function() reads that stored role and calls the core WordPress WP_User::add_role() API with it directly. Because the plugin never cross-checks the requested role against its own admin-defined allow-list of assignable roles, any WordPress role slug - including 'administrator' - is accepted and granted to the newly created account.
Know when Custom User Registration Fields For Woocommerce gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Unauthenticated network request (PR:N/AV:N) to the Store API grants Administrator, fully compromising confidentiality, integrity, and availability; the config prerequisite is a deployment condition, not attacker complexity, so AC:L is retained.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
The Custom User Registration Fields for WooCommerce plugin for WordPress is vulnerable to Privilege Escalation in versions up to, and including, 2.2.3. This is due to the plugin accepting an attacker-controlled afreg_select_user_role value from the unauthenticated WooCommerce Store API /wc/store/v1/checkout request in the af_reg_checkout_data_to_order_meta_data_block() function, persisting it in order meta, and then passing it directly to WP_User::add_role() in the af_reg_custom_order_processing_function() function (hooked to woocommerce_thankyou) without validating against the plugin's admin-configured allowed role list. This makes it possible for unauthenticated attackers to elevate their privileges to Administrator by creating an account during checkout with a modified JSON body specifying administrator (or any other role slug) as the desired role. Note: The exploit requires the "User Role Selection" setting to be enabled.
Articles & Coverage 2
Executive ViewAI
The Addify Custom User Registration Fields for WooCommerce plugin (versions ≤2.2.3) contains an unauthenticated privilege escalation vulnerability that allows attackers to gain administrative access during checkout. Any WooCommerce store running this plugin with User Role Selection enabled faces immediate risk of complete administrative compromise without requiring valid credentials.
Disable the 'User Role Selection' feature within plugin configuration, or restrict access to the Store API checkout endpoint (/wc/store/v1/checkout) to authenticated users only if your WooCommerce architecture permits. These mitigations reduce attack surface but do not eliminate the vulnerability; complete remediation requires plugin removal or vendor patch deployment.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.
EUVD-2026-68134
GHSA-8fc6-vv8j-hx7j
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB