CVE-2025-69970

CRITICALNVD 9.39.3
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.3 under NVD CVSS v3. EPSS exploit probability: 0.5% (43rd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 3 sources updated this week
9.3EG
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.5%CVSS: 9.3Exploit: None knownExposed services: Not assessed

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

FUXA v1.2.7 contains an insecure default configuration vulnerability in server/settings.default.js. The 'secureEnabled' flag is commented out by default, causing the application to initialize with authentication disabled. This allows unauthenticated remote attackers to access sensitive API endpoints, modify projects, and control industrial equipment immediately after installation.

CVSS v3
9.3
EG Score
9.3CRITICALmedium confidence
EG Risk
57
EG Risk 57/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)
Severity93% × 45%
Impact severity (EG Severity): CVSS 9.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 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: No fix is confirmed yet. Restrict network exposure of the affected system within your standard update timelines at low or medium mission impact and sooner than that at high, and watch for a fix.
EPSS PROB
0.5%
EPSS %ILE
43rd
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 (9.3): severity, escalated by confirmed exploitation. This CVE's 9.3 is its impact severity (EG Severity), not escalated.

EG Severity
9.3 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-19). 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).

No fix is confirmed yet. Restrict network exposure of the affected system within your standard update timelines at low or medium mission impact and sooner than that at high, and watch for a fix.

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

February 3, 2026

Last Modified

June 17, 2026

Advisory Details (1)

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

FUXA/server/settings.default.js at master · frangoteam/FUXA · GitHub

https://github.com/frangoteam/FUXA/blob/master/server/settings.default.js

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npmfuxa-server—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
fuxa-server—
  • every version through 1.2.7: no fix on record
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 20× in last 7d / 45× 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.

Showing the most recent 99 of 219 refreshes on record for this CVE.

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. 1 repeat row among the latest 100 is merged into the row it repeats. The 120 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-19 16:48 UTCEG score recompute
  2. 2026-10-19 16:48 UTCGHSA enrichmentGHSA-r5m2-fqcf-qrf7 · GitHub severity HIGH
  3. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  4. 2026-10-18 17:36 UTCEG score recompute
  5. 2026-10-18 17:36 UTCGHSA enrichmentGHSA-r5m2-fqcf-qrf7 · GitHub severity HIGH
  6. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  7. 2026-10-18 05:16 UTCEG score recompute
  8. 2026-10-17 18:26 UTCEG score recompute
  9. 2026-10-17 18:26 UTCGHSA enrichmentGHSA-r5m2-fqcf-qrf7 · GitHub severity HIGH
  10. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  11. 2026-10-16 19:17 UTCEG score recompute
  12. 2026-10-16 19:17 UTCGHSA enrichmentGHSA-r5m2-fqcf-qrf7 · GitHub severity HIGH
  13. 2026-10-16 16:39 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  14. 2026-10-15 16:44 UTCEG score recompute
  15. 2026-10-15 16:44 UTCGHSA enrichmentGHSA-r5m2-fqcf-qrf7 · GitHub severity HIGH
  16. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  17. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  18. 2026-10-14 10:47 UTCEG score recompute
  19. 2026-10-14 10:46 UTCGHSA enrichmentGHSA-r5m2-fqcf-qrf7 · GitHub severity HIGH
  20. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  21. 2026-10-13 09:16 UTCGHSA enrichmentGHSA-r5m2-fqcf-qrf7 · GitHub severity HIGH
  22. 2026-10-12 16:46 UTCEG score recompute
  23. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  24. 2026-10-12 10:06 UTCGHSA enrichmentGHSA-r5m2-fqcf-qrf7 · GitHub severity HIGH
  25. 2026-10-11 20:20 UTCEG score recompute
Show 74 more
  1. 2026-10-11 18:33 UTCEG score recompute
  2. 2026-10-11 15:07 UTCEG score recompute
  3. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  4. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  5. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  6. 2026-10-09 09:28 UTCOSV refresh
  7. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  8. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  9. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  10. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  11. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  12. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  13. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  14. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  15. 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  16. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  17. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  18. 2026-09-24 14:02 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  19. 2026-09-23 13:47 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  20. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  21. 2026-09-19 17:00 UTCOSV refresh
  22. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  23. 2026-09-17 19:30 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  24. 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  25. 2026-09-16 05:14 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  26. 2026-09-15 03:10 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  27. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  28. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  29. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  30. 2026-09-11 09:36 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  31. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  32. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  33. 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  34. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  35. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  36. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  37. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  38. 2026-08-31 20:05 UTCOSV refresh
  39. 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  40. 2026-08-28 21:40 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  41. 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  42. 2026-08-26 14:45 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  43. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  44. 2026-08-24 14:16 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  45. 2026-08-23 00:18 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  46. 2026-08-21 23:48 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  47. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  48. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  49. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  50. 2026-08-17 13:46 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  51. 2026-08-16 14:55 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  52. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  53. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  54. 2026-08-14 22:58 UTCGHSA enrichmentGHSA-r5m2-fqcf-qrf7 · GitHub severity HIGH
  55. 2026-08-14 15:07 UTCGHSA enrichmentGHSA-r5m2-fqcf-qrf7 · GitHub severity HIGH
  56. 2026-08-14 11:28 UTCEG score recompute
  57. 2026-08-14 11:28 UTCGHSA enrichmentGHSA-r5m2-fqcf-qrf7 · GitHub severity HIGH
  58. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  59. 2026-08-13 03:42 UTCEG score recompute
  60. 2026-08-13 03:42 UTCGHSA enrichmentGHSA-r5m2-fqcf-qrf7 · GitHub severity HIGH
  61. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  62. 2026-08-11 13:42 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  63. 2026-08-10 23:59 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  64. 2026-08-10 10:00 UTCGHSA enrichmentGHSA-r5m2-fqcf-qrf7 · GitHub severity HIGH
  65. 2026-08-10 03:18 UTCGHSA enrichmentGHSA-r5m2-fqcf-qrf7 · GitHub severity HIGH
  66. 2026-08-09 23:20 UTCGHSA enrichmentGHSA-r5m2-fqcf-qrf7 · GitHub severity HIGH
  67. 2026-08-09 19:41 UTCGHSA enrichmentGHSA-r5m2-fqcf-qrf7 · GitHub severity HIGH
  68. 2026-08-09 16:02 UTCEG score recompute
  69. 2026-08-09 16:02 UTCGHSA enrichmentGHSA-r5m2-fqcf-qrf7 · GitHub severity HIGH
  70. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  71. 2026-08-08 16:36 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  72. 2026-08-08 09:55 UTCGHSA enrichmentGHSA-r5m2-fqcf-qrf7 · GitHub severity HIGH
  73. 2026-08-08 06:16 UTCGHSA enrichmentGHSA-r5m2-fqcf-qrf7 · GitHub severity HIGH
  74. 2026-08-08 02:37 UTCGHSA enrichmentGHSA-r5m2-fqcf-qrf7 · GitHub severity HIGH

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2025-69970?
CVE-2025-69970 is a critical-severity vulnerability; its CVE record was published on February 3, 2026. FUXA v1.2.7 contains an insecure default configuration vulnerability in server/settings.default.js. The 'secureEnabled' flag is commented out by default, causing the application to initialize with authentication disabled. This allows unauthenticated remote attackers to access sensitive API…
When was the CVE record for CVE-2025-69970 published?
The CVE record for CVE-2025-69970 was published on February 3, 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 June 17, 2026; the record at its source may have been updated since.
Is CVE-2025-69970 actively exploited?
CVE-2025-69970 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (43rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-69970?
CVE-2025-69970 has a CVSS v3 base score of 9.3 (NVD).
How do I remediate CVE-2025-69970?
No fix for CVE-2025-69970 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-69970

Explore →

Is Your Infrastructure Affected by CVE-2025-69970?

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

Book a Demo →Browse All CVEs