CVE-2025-14815

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.1% (below the 1st 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

Also known asEUVD-2025-209294 (ENISA EUVD) · GHSA-p3rg-2cj3-m987 (GitHub Security Advisories)Source: ENISA EUVD

9.3EG
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).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.1%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.

Cleartext Storage of Sensitive Information vulnerability in Mitsubishi Electric GENESIS64 versions 10.97.3 and prior, Mitsubishi Electric ICONICS Suite versions 10.97.3 and prior, Mitsubishi Electric MobileHMI versions 10.97.3 and prior, Mitsubishi Electric Hyper Historian versions 10.97.3 and prior, Mitsubishi Electric AnalytiX versions 10.97.3 and prior, Mitsubishi Electric GENESIS versions 11.02 and prior, Mitsubishi Electric MC Works64 all versions, Mitsubishi Electric Iconics Digital Solutions GENESIS64 versions 10.97.3 and prior, Mitsubishi Electric Iconics Digital Solutions ICONICS Suite versions 10.97.3 and prior, Mitsubishi Electric Iconics Digital Solutions MobileHMI versions 10.97.3 and prior, Mitsubishi Electric Iconics Digital Solutions Hyper Historian versions 10.97.3 and prior, Mitsubishi Electric Iconics Digital Solutions AnalytiX versions 10.97.3 and prior, and Mitsubishi Electric Iconics Digital Solutions GENESIS versions 11.02 and prior allows a local attacker to disclose the SQL Server credentials stored in plaintext within the local SQLite file by exploiting this vulnerability, when the local caching feature using SQLite is enabled and SQL authentication is used for the SQL Server authentication. As a result, the unauthorized attacker could access the SQL Server and disclose, tamper with, or destroy data on the server, potentially cause a denial-of-service (DoS) condition on the system.

CVSS v3
9.3
EG Score
9.3CRITICALmedium confidence
EG Risk
42
EG Risk 42/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.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
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 none (CISA Vulnrichment) · Automatable no (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. 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.1%
EPSS %ILE
below the 1st
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.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). 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: 14 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 none (CISA Vulnrichment) · Automatable no (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)14 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 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

April 8, 2026

Last Modified

July 24, 2026

Advisory Details (3)

Auto-updated Oct 8, 2026
No fix on record yet. Sources: cisa.
CISA

Mitsubishi Electric GENESIS64 and ICONICS Suite products | CISA

https://www.cisa.gov/news-events/ics-advisories/icsa-26-097-01
Web page

JVNVU#90646130: 複数の三菱電機製品における重要情報の平文保存の脆弱性

https://jvn.jp/vu/JVNVU90646130/

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 18× in last 7d / 70× 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 98 of 294 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. 2 repeat rows among the latest 100 are merged into the row they repeat. The 196 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2025-14815?
CVE-2025-14815 is a critical-severity vulnerability; its CVE record was published on April 8, 2026. Cleartext Storage of Sensitive Information vulnerability in Mitsubishi Electric GENESIS64 versions 10.97.3 and prior, Mitsubishi Electric ICONICS Suite versions 10.97.3 and prior, Mitsubishi Electric MobileHMI versions 10.97.3 and prior, Mitsubishi Electric Hyper Historian versions 10.97.3 and…
When was the CVE record for CVE-2025-14815 published?
The CVE record for CVE-2025-14815 was published on April 8, 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 July 24, 2026; the record at its source may have been updated since.
Is CVE-2025-14815 actively exploited?
CVE-2025-14815 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (below the 1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-14815?
CVE-2025-14815 has a CVSS v3 base score of 9.3 (NVD).
How do I remediate CVE-2025-14815?
No fix for CVE-2025-14815 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-2025-14815

Explore →

Is Your Infrastructure Affected by CVE-2025-14815?

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