# CVE-2023-5247: Path traversal in GX Works3

> Attackers can execute malicious code or cause denial of service by tricking users into opening crafted project files in Mitsubishi FA engineering software.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 30 Nov 2023
- **Updated:** 2 Dec 2024
- **Also known as:** GHSA-3q5h-r4qp-qqcg

## What is CVE-2023-5247?

CVE-2023-5247 is a high-severity path traversal vulnerability in Mitsubishi Electric Corporation GX Works3, published on 30 Nov 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Malicious Code Execution Vulnerability due to External Control of File Name or Path in multiple Mitsubishi Electric FA Engineering Software Products allows a malicious attacker to execute a malicious code by having legitimate users open a specially crafted project file, which could result in information disclosure, tampering and deletion, or a denial-of-service (DoS) condition.

Weakness: CWE-610 (Externally Controlled Reference to a Resource in Another Sphere), CWE-73 (External Control of File Name or Path)

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

It affects 4 products.


Products: Mitsubishielectric Gx Works3, Mitsubishielectric Melsoft Iq Appportal, Mitsubishielectric Melsoft Navigator, Mitsubishielectric Motion Control Setting.

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

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

## Is CVE-2023-5247 being exploited?

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

## Other vulnerabilities in Mitsubishi Electric Corporation GX Works3

- [CVE-2023-4088](https://insights.sbomify.com/CVE-2023-4088/): Malicious Code Execution Vulnerability in FA Engineering Software Products (critical 9.3)
- [CVE-2022-29830](https://insights.sbomify.com/CVE-2022-29830/): Hardcoded credentials in GX Works3 (critical 9.1)
- [CVE-2022-25164](https://insights.sbomify.com/CVE-2022-25164/): Information disclosure in GX Works3 (high 8.6)
- [CVE-2022-29831](https://insights.sbomify.com/CVE-2022-29831/): Hardcoded credentials in GX Works3 (high 7.5)
- [CVE-2022-29826](https://insights.sbomify.com/CVE-2022-29826/): Information disclosure in GX Works3 (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-5247 is a high-severity path traversal vulnerability in Mitsubishi Electric Corporation GX Works3, published on 30 Nov 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-5247 in the wild and no public exploit code.

Affected product: Mitsubishi Electric Corporation GX Works3. 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-5247/ (Markdown: https://insights.sbomify.com/CVE-2023-5247/index.md)
```

## Sources

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

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