CVE-2026-10522

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. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, EPSS, GitHub Security Advisory
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.3%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 (WPScan) lists MemberHero versions up to and including 6.9 as affected. No release containing a fix is confirmed on record.

The MemberHero WordPress plugin through 6.9 does not restrict which account fields can be supplied during its frontend registration process, allowing unauthenticated attackers to register a new user with an arbitrary role, including Administrator, leading to a full site takeover.

Version 6.9 is advertised as resolving this issue, but the fix is incomplete and the current version remains exploitable by unauthenticated attackers to obtain administrator access and to take over existing accounts. No version that fully addresses the issue is available at the time of this advisory.

Mitigation: deactivate and remove the MemberHero WordPress plugin through 6.9 until a version that fully resolves this issue is released. If the MemberHero WordPress plugin through 6.9 must stay active, disable public registration, restrict access to the registration functionality, and monitor the site for unexpected administrator accounts.

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.3% × 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.3%
EPSS %ILE
25th
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 3, 2026

Advisory Details (1)

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

Simple User Registration <= 6.9 – Unauthenticated Privilege Escalation to Administrator | CVE 2026-10522 | Plugin Vulnerabilities

https://wpscan.com/vulnerability/8d531f22-1e8b-4e35-adec-c9304f4f7a07/

Vendor Advisories for CVE-2026-10522(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 / 176× 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 269 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 169 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-10522?
CVE-2026-10522 is a critical-severity vulnerability; its CVE record was published on August 29, 2026. The MemberHero WordPress plugin through 6.9 does not restrict which account fields can be supplied during its frontend registration process, allowing unauthenticated attackers to register a new user with an arbitrary role, including Administrator, leading to a full site takeover. Version 6.9 is…
When was the CVE record for CVE-2026-10522 published?
The CVE record for CVE-2026-10522 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 3, 2026; the record at its source may have been updated since.
Is CVE-2026-10522 actively exploited?
CVE-2026-10522 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (25th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-10522?
CVE-2026-10522 has a CVSS v3.1 base score of 9.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-10522?
No fix for CVE-2026-10522 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 (WPScan) lists MemberHero versions up to and including 6.9 as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-10522 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-10522?

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