CVE-2026-15369: The Custom User Registration Fields for WooCommerce plugin for WordPress is vulnerable to Privilege Escalation in vulnerability
CVE-2026-15369 affects The Custom User Registration Fields for WooCommerce plugin for WordPress is vulnerable to Privilege Escalation in up to, and including, 2.2.3 The Custom User Registration Fields for WooCommerce plugin for WordPress. The published...
What happened
CVE-2026-15369 affects The Custom User Registration Fields for WooCommerce plugin for WordPress is vulnerable to Privilege Escalation in up to, and including, 2 2 3 The Custom User Registration Fields for WooCommerce plugin for WordPress. A security weakness in The Custom User Registration Fields for WooCommerce plugin for WordPress is vulnerable to Privilege Escalation in is being tracked as CVE-2026-15369. The available advisory information identifies up to, and including, 2 2 3 The Custom User Registration Fields for WooCommerce plugin for WordPress as affected versions.
The available description indicates that the vulnerable path can be reached remotely or from an untrusted network, so the exposure of The Custom User Registration Fields for WooCommerce plugin for WordPress is vulnerable to Privilege Escalation in becomes part of the attack condition. 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. A maximum-severity vulnerability in the GiveWP plugin for WordPress allows an unauthenticated attacker to execute arbitrary commands on the hosting server.
The published description indicates a remote or untrusted-network exploitation path. GiveWP WordPress donation plugin flaw lets hackers execute server commands.
Editorial note: this News Brief follows the available evidence and adds length only when additional facts or useful context are available. Where public reporting does not establish a specific victim sequence, CyberDeltaForce does not present one as fact.
What the reporting and advisory establish
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
A maximum-severity vulnerability in the GiveWP plugin for WordPress allows an unauthenticated attacker to execute arbitrary commands on the hosting server.
GiveWP WordPress donation plugin flaw lets hackers execute server commands
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
A security weakness in The Custom User Registration Fields for WooCommerce plugin for WordPress is vulnerable to Privilege Escalation in is being tracked as CVE-2026-15369. The available advisory information identifies up to, and including, 2.2.3 The Custom User Registration Fields for WooCommerce plugin for WordPress as affected versions. The available description indicates that the vulnerable path can be reached remotely or from an untrusted network, so the exposure of The Custom User Registration Fields for WooCommerce plugin for WordPress is vulnerable to Privilege Escalation in becomes part of the attack condition. A maximum-severity vulnerability in the GiveWP plugin for WordPress allows an unauthenticated attacker to execute arbitrary commands on the hosting server. GiveWP WordPress donation plugin flaw lets hackers execute server commands. 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.
What this means for your environment
Move from the published facts to the technical path, exposure conditions and defensive decisions that matter in a real environment.
Attack & Exploitation Path
The sequence below shows how the vulnerability can be reached and what successful exploitation can produce. Each stage is labeled by evidence status.
an affected The Custom User Registration Fields for WooCommerce plugin for WordPress is vulnerable to Privilege Escalation in instance is reachable from a network or remote position available to the attacker.
attacker-controlled network input reaches the vulnerable code path on the affected service.
the the reported vulnerability condition is triggered inside The Custom User Registration Fields for WooCommerce plugin for WordPress is vulnerable to Privilege Escalation in, creating the security boundary failure described by the advisory.
successful exploitation reaches the confidentiality, integrity or availability impact described in the vendor or vulnerability record.
Why this matters to you
CVE-2026-15369 matters because the practical risk is not the score alone — it is whether the affected technology or service up to, and including, 2 exists in your environment and whether the reported trigger or exposure path can reach it. The current severity is CRITICAL 9.8. No exploitation flag is currently present in the CDF data, but that does not remove the need to validate affected systems.
Does this deserve attention in my environment?
Check the conditions below against your use of the affected technology or service up to, and including, 2.
Select the conditions that are true in your environment. Leaving a condition unselected does not mean you are safe — it only means you have not marked it as applicable.
- Search endpoint, software and asset inventory for the affected technology or service up to, and including, 2.
- Confirm the vendor-recommended fixed version or mitigation and verify deployment, not just assignment, across affected assets.
- Review relevant endpoint, application, network or identity telemetry for activity associated with exploitation of the affected component.
- Track vendor and government guidance for any change in exploitation status while remediation is underway.
What remains unconfirmed
- Available reporting does not currently indicate exploitation, but that can change as vendor, government or threat-intelligence reporting develops.
Sources & References
Original reporting and technical references are kept here for readers who want to verify the facts. Publisher names stay out of the reading flow above.