CVE-2025-64059

LOWPre-NVD 1.81.8
EchelonGraph scoreMEDIUM confidence

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

Score 1.8 from GitHub Security Advisory (severity: LOW) published 2026-09-13. A secondary CVSS source baseline 1.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this weekElevated
1.8EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (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: 1.8Exploit: 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.

Grav 1.7.50.2 allows admins to enter JavaScript via the Home Page editor. NOTE: the relevance of this for stored XSS is disputed because admins are allowed to modify templates, install plugins, and upload other executable content.

CVSS v3
1.8
EG Score
1.8LOWmedium confidence
EG Risk
24
EG Risk 24/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)
Severity18% × 45%
The EG Score, 1.8 of 10.
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. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.3%
EPSS %ILE
20th
KEV
Not listed

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. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

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.

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

September 13, 2026

Last Modified

September 16, 2026

References (1)

Vendor Advisories for CVE-2025-64059(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 / 54× 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.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 2 repeat rows among the latest 59 are merged into the row they repeat.

  1. 2026-10-13 22:09 UTCEG score recompute
  2. 2026-10-13 22:09 UTCGHSA enrichmentGHSA-2x7f-7273-jx2j · GitHub severity LOW · GitHub CVSS 1.8
  3. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  4. 2026-10-12 16:50 UTCEG score recompute
  5. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  6. 2026-10-11 20:24 UTCEG score recompute
  7. 2026-10-11 18:36 UTCEG score recompute
  8. 2026-10-11 15:11 UTCEG score recompute
  9. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  10. 2026-10-11 06:40 UTCEG score recompute
  11. 2026-10-11 06:40 UTCGHSA enrichmentGHSA-2x7f-7273-jx2j · GitHub severity LOW · GitHub CVSS 1.8
  12. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  13. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  14. 2026-10-08 17:10 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  15. 2026-10-08 09:42 UTCEG score recompute
  16. 2026-10-08 09:42 UTCGHSA enrichmentGHSA-2x7f-7273-jx2j · GitHub severity LOW · GitHub CVSS 1.8
  17. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  18. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  19. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  20. 2026-10-05 16:18 UTCEG score recompute
  21. 2026-10-05 16:18 UTCGHSA enrichmentGHSA-2x7f-7273-jx2j · GitHub severity LOW · GitHub CVSS 1.8
  22. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  23. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  24. 2026-10-02 22:34 UTCEG score recompute
  25. 2026-10-02 22:34 UTCGHSA enrichmentGHSA-2x7f-7273-jx2j · GitHub severity LOW · GitHub CVSS 1.8
Show 32 more
  1. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  2. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  3. 2026-09-30 05:10 UTCEG score recompute
  4. 2026-09-30 05:10 UTCGHSA enrichmentGHSA-2x7f-7273-jx2j · GitHub severity LOW · GitHub CVSS 1.8
  5. 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  6. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  7. 2026-09-27 11:45 UTCEG score recompute
  8. 2026-09-27 11:45 UTCGHSA enrichmentGHSA-2x7f-7273-jx2j · GitHub severity LOW · GitHub CVSS 1.8
  9. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  10. 2026-09-24 18:13 UTCEG score recompute
  11. 2026-09-24 18:13 UTCGHSA enrichmentGHSA-2x7f-7273-jx2j · GitHub severity LOW · GitHub CVSS 1.8
  12. 2026-09-24 14:02 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  13. 2026-09-23 13:47 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  14. 2026-09-22 00:33 UTCEG score recompute
  15. 2026-09-22 00:33 UTCGHSA enrichmentGHSA-2x7f-7273-jx2j · GitHub severity LOW · GitHub CVSS 1.8
  16. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  17. 2026-09-19 15:42 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  18. 2026-09-19 07:10 UTCEG score recompute
  19. 2026-09-19 07:10 UTCGHSA enrichmentGHSA-2x7f-7273-jx2j · GitHub severity LOW · GitHub CVSS 1.8
  20. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  21. 2026-09-17 19:30 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  22. 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  23. 2026-09-16 13:46 UTCEG score recompute
  24. 2026-09-16 13:45 UTCGHSA enrichmentGHSA-2x7f-7273-jx2j · GitHub severity LOW · GitHub CVSS 1.8
  25. 2026-09-15 03:10 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  26. 2026-09-14 19:21 UTCEG score recompute
  27. 2026-09-14 19:21 UTCGHSA enrichmentGHSA-2x7f-7273-jx2j · GitHub severity LOW · GitHub CVSS 1.8
  28. 2026-09-14 18:40 UTCEG score recompute
  29. 2026-09-14 18:40 UTCGHSA enrichmentGHSA-2x7f-7273-jx2j · GitHub severity LOW · GitHub CVSS 1.8
  30. 2026-09-13 19:24 UTCEG score recompute
  31. 2026-09-13 18:59 UTCEG score recomputeFirst assessed: 1.8 LOW
  32. 2026-09-13 18:59 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2025-64059?
CVE-2025-64059 is a low-severity vulnerability; its CVE record was published on September 13, 2026. Grav 1.7.50.2 allows admins to enter JavaScript via the Home Page editor. NOTE: the relevance of this for stored XSS is disputed because admins are allowed to modify templates, install plugins, and upload other executable content.
When was the CVE record for CVE-2025-64059 published?
The CVE record for CVE-2025-64059 was published on September 13, 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 September 16, 2026; the record at its source may have been updated since.
Is CVE-2025-64059 actively exploited?
CVE-2025-64059 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (20th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-64059?
CVE-2025-64059 has a CVSS base score of 1.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2025-64059?
No fix for CVE-2025-64059 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-2025-64059 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2025-64059

Explore →

Is Your Infrastructure Affected by CVE-2025-64059?

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

Book a Demo →Browse All CVEs