# CVE-2023-0457: Information Disclosure Vulnerability in MELSEC Series

> Remote attackers can read plaintext credentials from project files to access FTP or Web servers on Mitsubishi MELSEC PLCs.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Mar 2023
- **Updated:** 5 Mar 2025
- **Also known as:** GHSA-wmp3-7qc8-4x9f

## What is CVE-2023-0457?

CVE-2023-0457 is a high-severity vulnerability in Mitsubishi Electric Corporation MELSEC iQ-F Series FX5-ENET, published on 3 Mar 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Plaintext Storage of a Password vulnerability in Mitsubishi Electric Corporation MELSEC iQ-F Series, MELSEC iQ-R Series, MELSEC-Q Series and MELSEC-L Series allows a remote unauthenticated attacker to disclose plaintext credentials stored in project files and login into FTP server or Web server.

Weakness: CWE-522 (Insufficiently Protected Credentials), CWE-256 (Plaintext Storage of a Password)

## Which versions are affected by CVE-2023-0457?

It affects 38 products.


Products: Mitsubishielectric Fx5-Enet\/Ip Firmware, Mitsubishielectric Fx5-Enet Firmware, Mitsubishielectric Fx5s-30mr\/Es Firmware, Mitsubishielectric Fx5s-30mt\/Es Firmware, Mitsubishielectric Fx5s-30mt\/Ess Firmware, Mitsubishielectric Fx5s-40mr\/Es Firmware, Mitsubishielectric Fx5s-40mt\/Es Firmware, Mitsubishielectric Fx5s-40mt\/Ess Firmware, Mitsubishielectric Fx5s-60mr\/Es Firmware, Mitsubishielectric Fx5s-60mt\/Es Firmware, Mitsubishielectric Fx5s-60mt\/Ess Firmware, Mitsubishielectric Fx5s-80mr\/Es Firmware, Mitsubishielectric Fx5s-80mt\/Es Firmware, Mitsubishielectric Fx5s-80mt\/Ess Firmware, Mitsubishielectric Fx5uc-32mr\/Ds-Ts Firmware, Mitsubishielectric Fx5uc-32mt\/D Firmware, Mitsubishielectric Fx5uc-32mt\/Ds-Ts Firmware, Mitsubishielectric Fx5uc-32mt\/Dss-Ts Firmware, Mitsubishielectric Fx5uc-32mt\/Dss Firmware, Mitsubishielectric Fx5uc-64mt\/D Firmware and 18 more.

## How do I fix CVE-2023-0457?

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

## Is CVE-2023-0457 being exploited?

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

## Other vulnerabilities in Mitsubishi Electric Corporation MELSEC iQ-F Series FX5-ENET

- [CVE-2023-2060](https://insights.sbomify.com/CVE-2023-2060/): Authentication bypass vulnerability in MELSEC iQ-R Series / iQ-F Series EtherNet/IP Modules (high 7.5)
- [CVE-2023-2063](https://insights.sbomify.com/CVE-2023-2063/): File upload in MELSEC iQ-F Series EtherNet/IP module FX5-ENET/IP (medium 6.3)
- [CVE-2023-2061](https://insights.sbomify.com/CVE-2023-2061/): Authentication bypass vulnerability in MELSEC iQ-R Series / iQ-F Series EtherNet/IP Modules (medium 6.2)
- [CVE-2023-2062](https://insights.sbomify.com/CVE-2023-2062/): Information Disclosure vulnerability in EtherNet/IP Configuration tools (medium 6.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-0457 and fix it if it is affected.

What it is: CVE-2023-0457 is a high-severity vulnerability in Mitsubishi Electric Corporation MELSEC iQ-F Series FX5-ENET, published on 3 Mar 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-0457 in the wild and no public exploit code.

Affected product: Mitsubishi Electric Corporation MELSEC iQ-F Series FX5-ENET. 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-2023-0457/ (Markdown: https://insights.sbomify.com/CVE-2023-0457/index.md)
```

## Sources

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

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