CVE-2026-94257

HIGHPre-NVD 8.18.1
EchelonGraph scoreHIGH confidence

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

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-10-10. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, EPSS, GitHub Security Advisory
Trending — 5 sources updated this week
8.1EG
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.2%CVSS: 8.1Exploit: 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 SMS Alert WordPress plugin before 4.0.1 does not bind the account whose password is being changed to the phone number that was actually verified during its OTP password reset, allowing unauthenticated attackers to set a new password on an arbitrary account, including an administrator, by verifying a one-time code sent to a phone number they control.

CVSS v3
8.1
EG Score
8.1HIGHhigh confidence
EG Risk
52
EG Risk 52/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)
Severity81% × 45%
The EG Score, 8.1 of 10.
Exploitation0.2% × 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 partial (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.2%
EPSS %ILE
12th
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 partial (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)14 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 partial (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

October 10, 2026

Last Modified

October 10, 2026

Advisory Details (1)

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

SMS Alert 3.9.6 – 4.0.0 – Unauthenticated Privilege Escalation via Arbitrary Password Reset | CVE 2026-94257 | Plugin Vulnerabilities

https://wpscan.com/vulnerability/4c32fa5b-4677-4f62-8856-fbe9c601fc36/

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

  1. 2026-10-12 01:54 UTCGHSA enrichmentGHSA-vphv-2c5j-m636 · GitHub severity HIGH · GitHub CVSS 8.1
  2. 2026-10-11 19:12 UTCEG score recompute
  3. 2026-10-11 16:27 UTCEG score recompute
  4. 2026-10-11 13:50 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  5. 2026-10-11 13:41 UTCEG score recompute
  6. 2026-10-11 13:25 UTCEG score recompute
  7. 2026-10-11 13:24 UTCGHSA enrichmentGHSA-vphv-2c5j-m636 · GitHub severity HIGH · GitHub CVSS 8.1
  8. 2026-10-11 00:53 UTCEG score recompute
  9. 2026-10-11 00:52 UTCGHSA enrichmentGHSA-vphv-2c5j-m636 · GitHub severity HIGH · GitHub CVSS 8.1
  10. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  11. 2026-10-10 12:22 UTCGHSA enrichmentGHSA-vphv-2c5j-m636
  12. 2026-10-10 12:10 UTCEG score recomputeFirst assessed: 8.1 HIGH
  13. 2026-10-10 12:10 UTCGHSA enrichmentGHSA-vphv-2c5j-m636
  14. 2026-10-10 12:10 UTCMITRE cvelistV5CVSS v3 → 8.1 · severity → HIGH
  15. 2026-10-10 06:21 UTCNVD update
  16. 2026-10-10 06:06 UTCEG score recompute
  17. 2026-10-10 06:05 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-94257?
CVE-2026-94257 is a high-severity vulnerability; its CVE record was published on October 10, 2026. The SMS Alert WordPress plugin before 4.0.1 does not bind the account whose password is being changed to the phone number that was actually verified during its OTP password reset, allowing unauthenticated attackers to set a new password on an arbitrary account, including an administrator, by…
When was the CVE record for CVE-2026-94257 published?
The CVE record for CVE-2026-94257 was published on October 10, 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 October 10, 2026; the record at its source may have been updated since.
Is CVE-2026-94257 actively exploited?
CVE-2026-94257 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (12th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-94257?
CVE-2026-94257 has a CVSS v3.1 base score of 8.1 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-94257?
No fix for CVE-2026-94257 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 vendor advisories EchelonGraph has for CVE-2026-94257 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-94257?

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