# CVE-2023-31756: Command injection in n/a

> Authenticated administrators can execute arbitrary OS commands via the X_TP_IfName parameter in the TP-Link Archer VR1600V web portal.

- **Severity:** Medium 6.7 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 May 2023
- **Updated:** 21 Jan 2025
- **Also known as:** GHSA-f8j8-3vc2-3fr9

## What is CVE-2023-31756?

CVE-2023-31756 is a medium-severity command injection vulnerability in n/a, published on 19 May 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A command injection vulnerability exists in the administrative web portal in TP-Link Archer VR1600V devices running firmware Versions <= 0.1.0. 0.9.1 v5006.0 Build 220518 Rel.32480n which allows remote attackers, authenticated to the administrative web portal as an administrator user to open an operating system level shell via the 'X_TP_IfName' parameter.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

It affects 1 product.


Products: Tp-Link Archer Vr1600v Firmware.

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

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

## Is CVE-2023-31756 being exploited?

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

Public exploit code:

- CVE-2023-31756 Proof of Concept - Remote Code Execution for Archer V1/V2 Routers (github_poc): https://github.com/StanleyJobsonAU/LongBow

## Fix prompt for AI coding agents

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

What it is: CVE-2023-31756 is a medium-severity command injection vulnerability in n/a, published on 19 May 2023. 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-2023-31756 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-31756/ (Markdown: https://insights.sbomify.com/CVE-2023-31756/index.md)
```

## Sources

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

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