CVE-2026-94169

CRITICALPre-NVD 10.010.0
EchelonGraph scoreHIGH confidence

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

Score 10.0 from GitHub Security Advisory (severity: CRITICAL) published 2026-10-16. The CNA's CVSS baseline 10.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: the CNA's CVSS, EPSS, GitHub Security Advisory
Trending — 4 sources updated this week
10.0EG
EchelonGraph verdictPlan a fixRemediate 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: 3.3%CVSS: 10.0Exploit: None knownExposed services: Not assessed

Update the WordPress The Grid plugin to the latest available version (at least 2.8.2) (from the CVE record's solution, Patchstack) — apply it.

Improper Control of Generation of Code ('Code Injection') vulnerability in Theme-one The Grid the-grid allows Command Injection.This issue affects The Grid: from n/a through 2.8.1.

CVSS v3
10.0
EG Score
10.0CRITICALhigh confidence
EG Risk
60
EG Risk 60/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity100% × 45%
Impact severity (EG Severity): CVSS 10.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation1.0% × 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: Update the WordPress The Grid plugin to the latest available version (at least 2.8.2) (from the CVE record's solution, Patchstack). Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
3.3%
EPSS %ILE
88th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (10.0): severity, escalated by confirmed exploitation. This CVE's 10.0 is its impact severity (EG Severity), not escalated.

EG Severity
10.0 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
3.3% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

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

Update the WordPress The Grid plugin to the latest available version (at least 2.8.2) (from the CVE record's solution, Patchstack). Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

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

October 16, 2026

Last Modified

October 16, 2026

Advisory Details (1)

Auto-updated Oct 16, 2026
Fix named in the CVE record's solution (Patchstack).

Vendor Advisories for CVE-2026-94169(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 / 24× 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-21 16:34 UTCEPSS rescoreEPSS 3.3% · 88th percentile
  2. 2026-10-20 22:04 UTCEG score recompute
  3. 2026-10-20 22:04 UTCGHSA enrichmentGHSA-mx9f-gh9h-q5j2 · GitHub severity CRITICAL · GitHub CVSS 10.0
  4. 2026-10-20 16:34 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  5. 2026-10-19 21:18 UTCEG score recompute
  6. 2026-10-19 21:18 UTCGHSA enrichmentGHSA-mx9f-gh9h-q5j2 · GitHub severity CRITICAL · GitHub CVSS 10.0
  7. 2026-10-19 16:33 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  8. 2026-10-18 20:19 UTCEG score recompute
  9. 2026-10-18 20:19 UTCGHSA enrichmentGHSA-mx9f-gh9h-q5j2 · GitHub severity CRITICAL · GitHub CVSS 10.0
  10. 2026-10-18 16:33 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  11. 2026-10-18 02:58 UTCEG score recompute
  12. 2026-10-17 19:36 UTCEG score recompute
  13. 2026-10-17 19:36 UTCGHSA enrichmentGHSA-mx9f-gh9h-q5j2 · GitHub severity CRITICAL · GitHub CVSS 10.0
  14. 2026-10-17 16:35 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  15. 2026-10-16 18:54 UTCEG score recompute
  16. 2026-10-16 18:54 UTCGHSA enrichmentGHSA-mx9f-gh9h-q5j2 · GitHub severity CRITICAL · GitHub CVSS 10.0
  17. 2026-10-16 16:45 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  18. 2026-10-16 15:31 UTCEG score recompute
  19. 2026-10-16 15:30 UTCGHSA enrichmentGHSA-mx9f-gh9h-q5j2 · GitHub severity CRITICAL · GitHub CVSS 10.0
  20. 2026-10-16 14:34 UTCEG score recompute
  21. 2026-10-16 14:34 UTCGHSA enrichmentGHSA-mx9f-gh9h-q5j2 · GitHub severity CRITICAL · GitHub CVSS 10.0
  22. 2026-10-16 07:25 UTCEG score recompute
  23. 2026-10-16 07:10 UTCEG score recomputeFirst assessed: 10.0 CRITICAL
  24. 2026-10-16 07:07 UTCMITRE cvelistV5first tracked

Public detection templates

(1 reference)

A public Nuclei detection template is referenced for this CVE. A detection template checks whether a system is affected; it is not necessarily exploit code.

  • Nucleihttp/cves/2026/CVE-2026-94169.yaml
    Recorded Oct 20, 2026

    The Grid <= 2.8.1 - Unauthenticated Code Injection

    Open source ↗

Frequently asked(5)

What is CVE-2026-94169?
CVE-2026-94169 is a critical-severity vulnerability; its CVE record was published on October 16, 2026. Improper Control of Generation of Code ('Code Injection') vulnerability in Theme-one The Grid the-grid allows Command Injection.This issue affects The Grid: from n/a through 2.8.1.
When was CVE-2026-94169 made public?
CVE-2026-94169 was made public on October 14, 2026: that is the date its CVE record's CNA, Patchstack, gives for when the vulnerability was made public. The CVE record itself was published on October 16, 2026. EchelonGraph's copy of the record carries a last-modified date of October 16, 2026; the record at its source may have been updated since.
Is CVE-2026-94169 actively exploited?
CVE-2026-94169 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3.3% probability of exploitation in the next 30 days (88th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-94169?
CVE-2026-94169 has a CVSS base score of 10.0 (the CNA's own assessment, by patchstack; NVD's own analysis pending).
How do I remediate CVE-2026-94169?
The CVE record's solution for CVE-2026-94169, written by its CNA Patchstack, names the fix: "Update the WordPress The Grid plugin to the latest available version (at least 2.8.2)." The vendor advisories EchelonGraph has for CVE-2026-94169 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-94169?

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