CVE-2026-71426

HIGHPre-NVD 7.17.1
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (27th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated

Also known asEUVD-2026-91020 (ENISA EUVD)Source: ENISA EUVD

7.1EG
EchelonGraph verdictPlan mitigationNo fix is confirmed yet: check with the vendor for a fixed release; until one is applied, restrict network exposure of the affected system on your normal schedule (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 7.1Exploit: No code on recordExposed services: Not assessed

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

GetSimple CMS is a content management system (CMS), and GetSimple CMS CE is the community edition of that CMS. In versions 3.3.22 and prior, an authenticated user with page-editing rights can store an arbitrary filesystem path in a page's template attribute. On the public front-end, this value is passed unsanitized to a PHP include() when the page is rendered. Because the include path is never confined, this allows directory-traversal Local File Inclusion: arbitrary local files are included (and, if they contain PHP, executed) when any visitor requests the page. At time of publication, there are no publicly available patches.

CVSS v3
7.1
EG Score
7.1HIGHmedium confidence
EG Risk
48
EG Risk 48/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)
Severity71% × 45%
Impact severity (EG Severity): CVSS 7.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (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. Check with the vendor for a fixed release; until one is applied, restrict network exposure of the affected system on your normal schedule.
EPSS PROB
0.3%
EPSS %ILE
27th
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 (7.1): severity, escalated by confirmed exploitation. This CVE's 7.1 is its impact severity (EG Severity), not escalated.

EG Severity
7.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). 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; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

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

No fix is confirmed yet. Check with the vendor for a fixed release; until one is applied, restrict network exposure of the affected system on your normal schedule.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (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 1, 2026

Last Modified

October 1, 2026

Advisory Details (1)

Auto-updated Oct 1, 2026
No fix on record yet. Sources: github.
GitHub advisoryMentions a patch (unverified)

Authenticated Stored Local File Inclusion (LFI) via page "template" field · Advisory · GetSimpleCMS-CE/GetSimpleCMS-CE · GitHub

https://github.com/GetSimpleCMS-CE/GetSimpleCMS-CE/security/advisories/GHSA-559q-hqrv-m84x

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 48× 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-11-01 16:35 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  2. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  3. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  4. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  5. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  6. 2026-10-27 21:08 UTCEG score recompute
  7. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  8. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  9. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  10. 2026-10-25 14:07 UTCEG score recompute
  11. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  12. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  13. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  14. 2026-10-22 11:54 UTCEG score recompute
  15. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  16. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  17. 2026-10-20 08:47 UTCEG score recompute
  18. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  19. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  20. 2026-10-18 03:17 UTCEG score recompute
  21. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  22. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  23. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  24. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  25. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.3% · 25th percentile
Show 27 more
  1. 2026-10-13 08:29 UTCEG score recompute
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  3. 2026-10-12 15:42 UTCEG score recompute
  4. 2026-10-11 19:28 UTCEG score recompute
  5. 2026-10-11 16:43 UTCEG score recompute
  6. 2026-10-11 14:04 UTCEG score recompute
  7. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  8. 2026-10-10 20:16 UTCEG score recompute
  9. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  10. 2026-10-10 07:34 UTCEG score recompute
  11. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  12. 2026-10-08 17:29 UTCEG score recompute
  13. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  14. 2026-10-08 04:46 UTCEG score recompute
  15. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  16. 2026-10-07 03:24 UTCEG score recompute
  17. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  18. 2026-10-06 02:02 UTCEG score recompute
  19. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  20. 2026-10-05 00:39 UTCEG score recompute
  21. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  22. 2026-10-03 23:17 UTCEG score recompute
  23. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  24. 2026-10-02 21:50 UTCEG score recompute
  25. 2026-10-01 20:29 UTCEG score recompute
  26. 2026-10-01 19:46 UTCEG score recomputeFirst assessed: 7.1 HIGH
  27. 2026-10-01 19:45 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-71426?
CVE-2026-71426 is a high-severity vulnerability; its CVE record was published on October 1, 2026. GetSimple CMS is a content management system (CMS), and GetSimple CMS CE is the community edition of that CMS. In versions 3.3.22 and prior, an authenticated user with page-editing rights can store an arbitrary filesystem path in a page's template attribute. On the public front-end, this value is…
When was the CVE record for CVE-2026-71426 published?
The CVE record for CVE-2026-71426 was published on October 1, 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 1, 2026; the record at its source may have been updated since.
Is CVE-2026-71426 actively exploited?
CVE-2026-71426 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (27th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-71426?
CVE-2026-71426 has a CVSS base score of 7.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-71426?
No fix for CVE-2026-71426 is confirmed yet. Until one is published, restrict network exposure of the affected system — for example, keep it off the internet or limit it to trusted networks — and watch for a fix.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-71426?

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

Book a Demo →Browse All CVEs