# CVE-2025-14816: Information disclosure in AnalytiX

> Local attackers can view plaintext SQL credentials in the GUI, enabling unauthorized database access, data tampering, and denial of service.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Apr 2026
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-78jj-x36v-3whq

## What is CVE-2025-14816?

CVE-2025-14816 is a critical vulnerability in Mitsubishi Electric Corporation AnalytiX, published on 8 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Cleartext Storage of Sensitive Information in GUI 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 displayed in plain text in the GUI of the Hyper Historian Splitter feature by exploiting this vulnerability, when 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.

Weakness: CWE-317 (Cleartext Storage of Sensitive Information in GUI)

## Which versions are affected by CVE-2025-14816?


## How do I fix CVE-2025-14816?

No fix has been published for CVE-2025-14816 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-14816 being exploited?

There is no known exploitation of CVE-2025-14816 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-14816 and fix it if it is affected.

What it is: CVE-2025-14816 is a critical vulnerability in Mitsubishi Electric Corporation AnalytiX, published on 8 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-14816 in the wild and no public exploit code.

Affected product: Mitsubishi Electric Corporation AnalytiX. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-14816/ (Markdown: https://insights.sbomify.com/CVE-2025-14816/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-14816
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-14816
- OSV: https://osv.dev/vulnerability/CVE-2025-14816

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-14816/
Summaries are generated and may contain mistakes; the official description above is the record.