CVE-2026-62106

HIGHPre-NVD 8.88.8—
EchelonGraph scoreHIGH confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-09-11. a secondary CVSS source baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: None knownExposed: 0

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

Subscriber Privilege Escalation in SMS Alert Order Notifications <= 3.9.9 versions.

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

Published

September 11, 2026

Last Modified

September 11, 2026

Advisory Details (1)

Auto-updated Sep 11, 2026
No patch confirmed yet.
generic

Privilege Escalation in WordPress SMS Alert Order Notifications Plugin - Patchstack

https://patchstack.com/database/wordpress/plugin/sms-alert/vulnerability/wordpress-sms-alert-order-notifications-plugin-3-9-9-privilege-escalation-vulnerability?_s_id=cve

Vendor Advisories for CVE-2026-62106(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 24× in last 7d / 33× 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-20 12:47 UTCGHSA enrichment
  2. 2026-09-20 00:37 UTCEG score recompute
  3. 2026-09-20 00:37 UTCGHSA enrichment
  4. 2026-09-19 12:27 UTCGHSA enrichment
  5. 2026-09-19 00:17 UTCEG score recompute
  6. 2026-09-19 00:17 UTCGHSA enrichment
  7. 2026-09-18 19:28 UTCEPSS rescore
  8. 2026-09-18 12:07 UTCGHSA enrichment
  9. 2026-09-17 23:57 UTCEG score recompute
  10. 2026-09-17 23:57 UTCGHSA enrichment
  11. 2026-09-17 11:47 UTCGHSA enrichment
  12. 2026-09-16 23:37 UTCEG score recompute
  13. 2026-09-16 23:37 UTCGHSA enrichment
  14. 2026-09-16 14:08 UTCEPSS rescore
  15. 2026-09-16 11:26 UTCEG score recompute
  16. 2026-09-16 11:26 UTCGHSA enrichment
  17. 2026-09-16 05:15 UTCEPSS rescore
  18. 2026-09-15 23:17 UTCGHSA enrichment
  19. 2026-09-15 10:38 UTCEG score recompute
  20. 2026-09-15 10:38 UTCGHSA enrichment
  21. 2026-09-14 22:23 UTCGHSA enrichment
  22. 2026-09-14 10:12 UTCGHSA enrichment
  23. 2026-09-13 22:02 UTCEG score recompute
  24. 2026-09-13 22:02 UTCGHSA enrichment
  25. 2026-09-13 09:52 UTCGHSA enrichment
Show 8 more
  1. 2026-09-12 21:41 UTCEG score recompute
  2. 2026-09-12 21:41 UTCGHSA enrichment
  3. 2026-09-12 09:31 UTCEG score recompute
  4. 2026-09-12 09:31 UTCGHSA enrichment
  5. 2026-09-11 20:18 UTCEG score recompute
  6. 2026-09-11 19:34 UTCEG score recompute
  7. 2026-09-11 18:19 UTCEG score recompute
  8. 2026-09-11 18:18 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-62106?
CVE-2026-62106 is a high vulnerability published on September 11, 2026. Subscriber Privilege Escalation in SMS Alert Order Notifications <= 3.9.9 versions.
When was CVE-2026-62106 disclosed?
CVE-2026-62106 was first published in the National Vulnerability Database on September 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-62106 actively exploited?
CVE-2026-62106 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 75.3% of all scored CVEs.
What is the CVSS score of CVE-2026-62106?
CVE-2026-62106 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-62106?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-62106, 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-62106

Explore →

Is Your Infrastructure Affected by CVE-2026-62106?

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

Start Free Scan →Browse All CVEs