CVE-2026-15369

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

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.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this week
9.8EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 9.8Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

The CVE record's CNA (Wordfence) lists Addify Custom User Registration Fields for WooCommerce versions up to and including 2.2.3 as affected. No release containing a fix is confirmed on record.

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.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
59
EG Risk 59/100

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 computed (value × EchelonGraph’s weight)
Severity98% × 45%
The EG Score, 9.8 of 10.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.4%
EPSS %ILE
32nd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 29, 2026

Last Modified

September 1, 2026

Advisory Details (1)

Auto-updated Oct 13, 2026
No fix on record yet.
Web page

Custom 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 28× in last 7d / 195× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 326 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 226 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-14 14:08 UTCEG score recompute
  2. 2026-10-14 14:07 UTCGHSA enrichmentGHSA-8fc6-vv8j-hx7j · GitHub severity CRITICAL · GitHub CVSS 9.8
  3. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  4. 2026-10-13 11:54 UTCEG score recompute
  5. 2026-10-13 11:53 UTCGHSA enrichmentGHSA-8fc6-vv8j-hx7j · GitHub severity CRITICAL · GitHub CVSS 9.8
  6. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  7. 2026-10-12 16:32 UTCEG score recompute
  8. 2026-10-12 09:39 UTCGHSA enrichmentGHSA-8fc6-vv8j-hx7j · GitHub severity CRITICAL · GitHub CVSS 9.8
  9. 2026-10-11 20:10 UTCEG score recompute
  10. 2026-10-11 17:22 UTCEG score recompute
  11. 2026-10-11 14:55 UTCEG score recompute
  12. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  13. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  14. 2026-10-10 13:20 UTCGHSA enrichmentGHSA-8fc6-vv8j-hx7j · GitHub severity CRITICAL · GitHub CVSS 9.8
  15. 2026-10-10 09:35 UTCGHSA enrichmentGHSA-8fc6-vv8j-hx7j · GitHub severity CRITICAL · GitHub CVSS 9.8
  16. 2026-10-10 05:14 UTCGHSA enrichmentGHSA-8fc6-vv8j-hx7j · GitHub severity CRITICAL · GitHub CVSS 9.8
  17. 2026-10-10 00:45 UTCEG score recompute
  18. 2026-10-10 00:45 UTCGHSA enrichmentGHSA-8fc6-vv8j-hx7j · GitHub severity CRITICAL · GitHub CVSS 9.8
  19. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  20. 2026-10-09 06:18 UTCGHSA enrichmentGHSA-8fc6-vv8j-hx7j · GitHub severity CRITICAL · GitHub CVSS 9.8
  21. 2026-10-09 02:33 UTCEG score recompute
  22. 2026-10-09 02:33 UTCGHSA enrichmentGHSA-8fc6-vv8j-hx7j · GitHub severity CRITICAL · GitHub CVSS 9.8
  23. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  24. 2026-10-08 08:18 UTCGHSA enrichmentGHSA-8fc6-vv8j-hx7j · GitHub severity CRITICAL · GitHub CVSS 9.8
  25. 2026-10-08 04:33 UTCGHSA enrichmentGHSA-8fc6-vv8j-hx7j · GitHub severity CRITICAL · GitHub CVSS 9.8
Show 75 more
  1. 2026-10-08 00:45 UTCEG score recompute
  2. 2026-10-08 00:45 UTCGHSA enrichmentGHSA-8fc6-vv8j-hx7j · GitHub severity CRITICAL · GitHub CVSS 9.8
  3. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  4. 2026-10-07 09:50 UTCGHSA enrichmentGHSA-8fc6-vv8j-hx7j · GitHub severity CRITICAL · GitHub CVSS 9.8
  5. 2026-10-07 05:55 UTCGHSA enrichmentGHSA-8fc6-vv8j-hx7j · GitHub severity CRITICAL · GitHub CVSS 9.8
  6. 2026-10-07 02:10 UTCGHSA enrichmentGHSA-8fc6-vv8j-hx7j · GitHub severity CRITICAL · GitHub CVSS 9.8
  7. 2026-10-06 22:26 UTCGHSA enrichmentGHSA-8fc6-vv8j-hx7j · GitHub severity CRITICAL · GitHub CVSS 9.8
  8. 2026-10-06 18:42 UTCEG score recompute
  9. 2026-10-06 18:42 UTCGHSA enrichmentGHSA-8fc6-vv8j-hx7j · GitHub severity CRITICAL · GitHub CVSS 9.8
  10. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  11. 2026-10-06 14:57 UTCGHSA enrichmentGHSA-8fc6-vv8j-hx7j · GitHub severity CRITICAL · GitHub CVSS 9.8
  12. 2026-10-06 11:11 UTCGHSA enrichmentGHSA-8fc6-vv8j-hx7j · GitHub severity CRITICAL · GitHub CVSS 9.8
  13. 2026-10-06 07:27 UTCGHSA enrichmentGHSA-8fc6-vv8j-hx7j · GitHub severity CRITICAL · GitHub CVSS 9.8
  14. 2026-10-06 00:47 UTCGHSA enrichmentGHSA-8fc6-vv8j-hx7j · GitHub severity CRITICAL · GitHub CVSS 9.8
  15. 2026-10-05 20:32 UTCEG score recompute
  16. 2026-10-05 20:32 UTCGHSA enrichmentGHSA-8fc6-vv8j-hx7j · GitHub severity CRITICAL · GitHub CVSS 9.8
  17. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  18. 2026-10-05 16:49 UTCGHSA enrichmentGHSA-8fc6-vv8j-hx7j · GitHub severity CRITICAL · GitHub CVSS 9.8
  19. 2026-10-05 12:45 UTCGHSA enrichmentGHSA-8fc6-vv8j-hx7j · GitHub severity CRITICAL · GitHub CVSS 9.8
  20. 2026-10-05 09:00 UTCGHSA enrichmentGHSA-8fc6-vv8j-hx7j · GitHub severity CRITICAL · GitHub CVSS 9.8
  21. 2026-10-05 05:05 UTCGHSA enrichmentGHSA-8fc6-vv8j-hx7j · GitHub severity CRITICAL · GitHub CVSS 9.8
  22. 2026-10-05 01:20 UTCEG score recompute
  23. 2026-10-05 01:20 UTCGHSA enrichmentGHSA-8fc6-vv8j-hx7j · GitHub severity CRITICAL · GitHub CVSS 9.8
  24. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  25. 2026-10-04 20:34 UTCGHSA enrichmentGHSA-8fc6-vv8j-hx7j · GitHub severity CRITICAL · GitHub CVSS 9.8
  26. 2026-10-04 16:14 UTCGHSA enrichmentGHSA-8fc6-vv8j-hx7j · GitHub severity CRITICAL · GitHub CVSS 9.8
  27. 2026-10-04 12:30 UTCGHSA enrichmentGHSA-8fc6-vv8j-hx7j · GitHub severity CRITICAL · GitHub CVSS 9.8
  28. 2026-10-04 08:45 UTCGHSA enrichmentGHSA-8fc6-vv8j-hx7j · GitHub severity CRITICAL · GitHub CVSS 9.8
  29. 2026-10-04 04:58 UTCGHSA enrichmentGHSA-8fc6-vv8j-hx7j · GitHub severity CRITICAL · GitHub CVSS 9.8
  30. 2026-10-04 01:13 UTCGHSA enrichmentGHSA-8fc6-vv8j-hx7j · GitHub severity CRITICAL · GitHub CVSS 9.8
  31. 2026-10-03 21:08 UTCGHSA enrichmentGHSA-8fc6-vv8j-hx7j · GitHub severity CRITICAL · GitHub CVSS 9.8
  32. 2026-10-03 17:20 UTCEG score recompute
  33. 2026-10-03 17:20 UTCGHSA enrichmentGHSA-8fc6-vv8j-hx7j · GitHub severity CRITICAL · GitHub CVSS 9.8
  34. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  35. 2026-10-03 13:36 UTCGHSA enrichmentGHSA-8fc6-vv8j-hx7j · GitHub severity CRITICAL · GitHub CVSS 9.8
  36. 2026-10-03 05:16 UTCGHSA enrichmentGHSA-8fc6-vv8j-hx7j · GitHub severity CRITICAL · GitHub CVSS 9.8
  37. 2026-10-03 01:32 UTCGHSA enrichmentGHSA-8fc6-vv8j-hx7j · GitHub severity CRITICAL · GitHub CVSS 9.8
  38. 2026-10-02 21:34 UTCGHSA enrichmentGHSA-8fc6-vv8j-hx7j · GitHub severity CRITICAL · GitHub CVSS 9.8
  39. 2026-10-02 17:50 UTCEG score recompute
  40. 2026-10-02 17:50 UTCGHSA enrichmentGHSA-8fc6-vv8j-hx7j · GitHub severity CRITICAL · GitHub CVSS 9.8
  41. 2026-10-02 14:01 UTCGHSA enrichmentGHSA-8fc6-vv8j-hx7j · GitHub severity CRITICAL · GitHub CVSS 9.8
  42. 2026-10-02 09:58 UTCGHSA enrichmentGHSA-8fc6-vv8j-hx7j · GitHub severity CRITICAL · GitHub CVSS 9.8
  43. 2026-10-02 06:14 UTCGHSA enrichmentGHSA-8fc6-vv8j-hx7j · GitHub severity CRITICAL · GitHub CVSS 9.8
  44. 2026-10-02 00:36 UTCEG score recompute
  45. 2026-10-02 00:36 UTCGHSA enrichmentGHSA-8fc6-vv8j-hx7j · GitHub severity CRITICAL · GitHub CVSS 9.8
  46. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  47. 2026-10-01 19:47 UTCGHSA enrichmentGHSA-8fc6-vv8j-hx7j · GitHub severity CRITICAL · GitHub CVSS 9.8
  48. 2026-10-01 12:51 UTCGHSA enrichmentGHSA-8fc6-vv8j-hx7j · GitHub severity CRITICAL · GitHub CVSS 9.8
  49. 2026-10-01 09:07 UTCGHSA enrichmentGHSA-8fc6-vv8j-hx7j · GitHub severity CRITICAL · GitHub CVSS 9.8
  50. 2026-10-01 05:24 UTCGHSA enrichmentGHSA-8fc6-vv8j-hx7j · GitHub severity CRITICAL · GitHub CVSS 9.8
  51. 2026-10-01 00:58 UTCGHSA enrichmentGHSA-8fc6-vv8j-hx7j · GitHub severity CRITICAL · GitHub CVSS 9.8
  52. 2026-09-30 19:47 UTCEG score recompute
  53. 2026-09-30 19:47 UTCGHSA enrichmentGHSA-8fc6-vv8j-hx7j · GitHub severity CRITICAL · GitHub CVSS 9.8
  54. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  55. 2026-09-30 11:31 UTCGHSA enrichmentGHSA-8fc6-vv8j-hx7j · GitHub severity CRITICAL · GitHub CVSS 9.8
  56. 2026-09-30 07:32 UTCGHSA enrichmentGHSA-8fc6-vv8j-hx7j · GitHub severity CRITICAL · GitHub CVSS 9.8
  57. 2026-09-30 03:48 UTCGHSA enrichmentGHSA-8fc6-vv8j-hx7j · GitHub severity CRITICAL · GitHub CVSS 9.8
  58. 2026-09-29 16:07 UTCEG score recompute
  59. 2026-09-29 16:07 UTCGHSA enrichmentGHSA-8fc6-vv8j-hx7j · GitHub severity CRITICAL · GitHub CVSS 9.8
  60. 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  61. 2026-09-29 12:09 UTCGHSA enrichmentGHSA-8fc6-vv8j-hx7j · GitHub severity CRITICAL · GitHub CVSS 9.8
  62. 2026-09-29 08:21 UTCGHSA enrichmentGHSA-8fc6-vv8j-hx7j · GitHub severity CRITICAL · GitHub CVSS 9.8
  63. 2026-09-29 04:37 UTCGHSA enrichmentGHSA-8fc6-vv8j-hx7j · GitHub severity CRITICAL · GitHub CVSS 9.8
  64. 2026-09-29 00:52 UTCEG score recompute
  65. 2026-09-29 00:52 UTCGHSA enrichmentGHSA-8fc6-vv8j-hx7j · GitHub severity CRITICAL · GitHub CVSS 9.8
  66. 2026-09-28 21:07 UTCGHSA enrichmentGHSA-8fc6-vv8j-hx7j · GitHub severity CRITICAL · GitHub CVSS 9.8
  67. 2026-09-28 15:46 UTCEG score recompute
  68. 2026-09-28 15:46 UTCGHSA enrichmentGHSA-8fc6-vv8j-hx7j · GitHub severity CRITICAL · GitHub CVSS 9.8
  69. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  70. 2026-09-28 11:50 UTCGHSA enrichmentGHSA-8fc6-vv8j-hx7j · GitHub severity CRITICAL · GitHub CVSS 9.8
  71. 2026-09-28 08:06 UTCGHSA enrichmentGHSA-8fc6-vv8j-hx7j · GitHub severity CRITICAL · GitHub CVSS 9.8
  72. 2026-09-28 04:20 UTCGHSA enrichmentGHSA-8fc6-vv8j-hx7j · GitHub severity CRITICAL · GitHub CVSS 9.8
  73. 2026-09-28 00:36 UTCGHSA enrichmentGHSA-8fc6-vv8j-hx7j · GitHub severity CRITICAL · GitHub CVSS 9.8
  74. 2026-09-27 20:52 UTCGHSA enrichmentGHSA-8fc6-vv8j-hx7j · GitHub severity CRITICAL · GitHub CVSS 9.8
  75. 2026-09-27 17:08 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-15369?
CVE-2026-15369 is a critical-severity vulnerability; its CVE record was published on August 29, 2026. 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 afregselectuserrole value from the unauthenticated WooCommerce Store API…
When was the CVE record for CVE-2026-15369 published?
The CVE record for CVE-2026-15369 was published on August 29, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 1, 2026; the record at its source may have been updated since.
Is CVE-2026-15369 actively exploited?
CVE-2026-15369 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (32nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-15369?
CVE-2026-15369 has a CVSS base score of 9.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-15369?
No fix for CVE-2026-15369 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's CNA (Wordfence) lists Addify Custom User Registration Fields for WooCommerce versions up to and including 2.2.3 as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-15369 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-15369

Explore →

Is Your Infrastructure Affected by CVE-2026-15369?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs