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.
CVE-2026-15369
Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-29. a secondary CVSS source baseline 9.8; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.8
- EG Score
- 9.8(high)
- EG Risk
- 49(Track)EG Risk 49/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity98% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
August 29, 2026
Last Modified
August 29, 2026
Advisory Details (1)
Auto-updated Aug 29, 2026Custom User Registration Fields for WooCommerce - WooCommerce Marketplace
https://woocommerce.com/products/custom-user-registration-fields-for-woocommerce/Vendor Advisories for CVE-2026-15369(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 6× in last 7d / 6× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-30 03:50 UTCGHSA enrichment
- 2026-08-30 00:06 UTCEG score recompute
- 2026-08-30 00:06 UTCGHSA enrichment
- 2026-08-29 20:21 UTCEG score recompute
- 2026-08-29 19:34 UTCEG score recompute
- 2026-08-29 19:32 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-269
Frequently asked(4)
What is CVE-2026-15369?
When was CVE-2026-15369 disclosed?
What is the CVSS score of CVE-2026-15369?
How do I remediate CVE-2026-15369?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-15369
Is Your Infrastructure Affected by CVE-2026-15369?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.