CVE-2026-83628

MEDIUMPre-NVD 4.34.3—
EchelonGraph scoreHIGH confidence

Score 4.3 from GitHub Security Advisory published 2026-09-05. a secondary CVSS source baseline 4.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
4.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.3Exploit: None knownExposed: 0

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

The Theme My Login plugin for WordPress is vulnerable to Missing Authorization in versions up to, and including, 7.1.15 on Multisite installations. This is due to the tml_ms_signup_handler() function's gimmeanotherblog branch failing to enforce the network's active_signup registration policy, checking only is_user_logged_in() while sibling branches such as validate-blog-signup apply the full policy gate. This makes it possible for authenticated attackers, with Subscriber-level access and above, to directly POST stage=gimmeanotherblog to Theme My Login's signup route, bypassing the configured registration policy entirely — even when it is set to none or user — which causes wpmu_create_blog() to execute with the attacker's user ID, after which WordPress core assigns the Administrator role on the newly created subsite via add_user_to_blog(). The privilege gain is scoped to the newly created subsite only; the attacker's account retains Subscriber-level access on the main site and does not obtain Super Admin or network-level capabilities such as manage_network or manage_sites.

CVSS v3
4.3
EG Score
4.3(high)
EG Risk
20(Track)
EG Risk 20/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 computed
Severity43% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
31%
KEV
Not listed

Published

September 5, 2026

Last Modified

September 8, 2026

References (7)

Vendor Advisories for CVE-2026-83628(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 20× in last 7d / 63× 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.

  1. 2026-09-25 12:15 UTCEG score recompute
  2. 2026-09-25 12:15 UTCGHSA enrichment
  3. 2026-09-24 14:04 UTCEPSS rescore
  4. 2026-09-24 13:42 UTCEG score recompute
  5. 2026-09-24 13:42 UTCGHSA enrichment
  6. 2026-09-23 17:54 UTCEPSS rescore
  7. 2026-09-23 15:09 UTCGHSA enrichment
  8. 2026-09-22 16:37 UTCEG score recompute
  9. 2026-09-22 16:37 UTCGHSA enrichment
  10. 2026-09-22 16:01 UTCEPSS rescore
  11. 2026-09-21 21:09 UTCEPSS rescore
  12. 2026-09-21 18:04 UTCEG score recompute
  13. 2026-09-21 18:04 UTCGHSA enrichment
  14. 2026-09-20 20:16 UTCEPSS rescore
  15. 2026-09-20 19:32 UTCGHSA enrichment
  16. 2026-09-19 21:00 UTCEG score recompute
  17. 2026-09-19 21:00 UTCGHSA enrichment
  18. 2026-09-18 22:28 UTCEG score recompute
  19. 2026-09-18 22:28 UTCGHSA enrichment
  20. 2026-09-18 19:28 UTCEPSS rescore
  21. 2026-09-17 23:56 UTCEG score recompute
  22. 2026-09-17 23:56 UTCGHSA enrichment
  23. 2026-09-17 19:32 UTCEPSS rescore
  24. 2026-09-17 01:11 UTCEG score recompute
  25. 2026-09-17 01:11 UTCGHSA enrichment
Show 38 more
  1. 2026-09-16 14:09 UTCEPSS rescore
  2. 2026-09-16 05:15 UTCEPSS rescore
  3. 2026-09-16 02:39 UTCGHSA enrichment
  4. 2026-09-15 04:06 UTCEG score recompute
  5. 2026-09-15 04:06 UTCGHSA enrichment
  6. 2026-09-15 03:12 UTCEPSS rescore
  7. 2026-09-15 03:12 UTCEPSS rescore
  8. 2026-09-14 05:34 UTCEG score recompute
  9. 2026-09-14 05:34 UTCGHSA enrichment
  10. 2026-09-13 07:01 UTCEG score recompute
  11. 2026-09-13 07:01 UTCGHSA enrichment
  12. 2026-09-12 08:29 UTCEG score recompute
  13. 2026-09-12 08:29 UTCGHSA enrichment
  14. 2026-09-11 14:53 UTCEPSS rescore
  15. 2026-09-11 14:53 UTCEPSS rescore
  16. 2026-09-11 09:56 UTCEG score recompute
  17. 2026-09-11 09:56 UTCGHSA enrichment
  18. 2026-09-10 11:24 UTCEG score recompute
  19. 2026-09-10 11:23 UTCGHSA enrichment
  20. 2026-09-09 12:50 UTCEG score recompute
  21. 2026-09-09 12:49 UTCGHSA enrichment
  22. 2026-09-08 22:01 UTCEPSS rescore
  23. 2026-09-08 14:16 UTCGHSA enrichment
  24. 2026-09-08 10:59 UTCEG score recompute
  25. 2026-09-08 10:59 UTCGHSA enrichment
  26. 2026-09-07 12:25 UTCEG score recompute
  27. 2026-09-07 12:24 UTCGHSA enrichment
  28. 2026-09-07 11:28 UTCEG score recompute
  29. 2026-09-07 11:28 UTCGHSA enrichment
  30. 2026-09-07 03:32 UTCEG score recompute
  31. 2026-09-07 03:31 UTCGHSA enrichment
  32. 2026-09-06 13:48 UTCEPSS rescore
  33. 2026-09-06 04:57 UTCEG score recompute
  34. 2026-09-06 04:57 UTCGHSA enrichment
  35. 2026-09-05 15:31 UTCEPSS rescore
  36. 2026-09-05 06:25 UTCEG score recompute
  37. 2026-09-05 05:39 UTCEG score recompute
  38. 2026-09-05 05:38 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-83628?
CVE-2026-83628 is a medium vulnerability published on September 5, 2026. The Theme My Login plugin for WordPress is vulnerable to Missing Authorization in versions up to, and including, 7.1.15 on Multisite installations. This is due to the tmlmssignuphandler() function's gimmeanotherblog branch failing to enforce the network's activesignup registration policy, checking…
When was CVE-2026-83628 disclosed?
CVE-2026-83628 was first published in the National Vulnerability Database on September 5, 2026, with the most recent update on September 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-83628 actively exploited?
CVE-2026-83628 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 69.2% of all scored CVEs.
What is the CVSS score of CVE-2026-83628?
CVE-2026-83628 has a CVSS v3 base score of 4.3 (NVD).
How do I remediate CVE-2026-83628?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-83628, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-83628?

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

Book a Demo →Browse All CVEs