# CVE-2023-31814: Path traversal in n/a

> Attackers can exploit a file inclusion vulnerability in D-Link DIR-300 routers to read sensitive files or execute arbitrary code.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 May 2023
- **Updated:** 17 Jan 2025
- **Also known as:** GHSA-7wrc-fqxq-c226

## What is CVE-2023-31814?

CVE-2023-31814 is a critical path traversal vulnerability in n/a, published on 23 May 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

D-Link DIR-300 firmware <=REVA1.06 and <=REVB2.06 is vulnerable to File inclusion via /model/__lang_msg.php.

Weakness: CWE-706 (Use of Incorrectly-Resolved Name or Reference)

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

It affects 1 product.


Products: Dlink Dir-300 Firmware.

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

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

## Is CVE-2023-31814 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2011-4723](https://insights.sbomify.com/CVE-2011-4723/): D-Link DIR-300 Router Cleartext Storage of a Password (medium 5.7, exploited in the wild)
- [CVE-2013-10069](https://insights.sbomify.com/CVE-2013-10069/): D-Link Devices Unauthenticated RCE (critical 10.0)
- [CVE-2013-7471](https://insights.sbomify.com/CVE-2013-7471/): Command injection in n/a (critical 9.8)
- [CVE-2013-10048](https://insights.sbomify.com/CVE-2013-10048/): D-Link Devices command.php Unauthenticated RCE (critical 9.3)
- [CVE-2024-41616](https://insights.sbomify.com/CVE-2024-41616/): Hardcoded credentials in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-31814 is a critical path traversal vulnerability in n/a, published on 23 May 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-31814 in the wild and no public exploit code.

Affected product: n/a. 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-31814/ (Markdown: https://insights.sbomify.com/CVE-2023-31814/index.md)
```

## Sources

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

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