# CVE-2017-13713: Command injection in n/a

> Remote authenticated attackers can execute arbitrary code on T&W WiFi Repeaters via shell metacharacters in the webupg CGI script.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Sep 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-9g3p-mgpx-m6fh

## What is CVE-2017-13713?

CVE-2017-13713 is a high-severity command injection vulnerability in n/a, published on 7 Sep 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

T&W WIFI Repeater BE126 allows remote authenticated users to execute arbitrary code via shell metacharacters in the user parameter to cgi-bin/webupg.

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

## Which versions are affected by CVE-2017-13713?

It affects 1 product.


Products: Twsz Wifi Repeater Firmware.

## How do I fix CVE-2017-13713?

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

## Is CVE-2017-13713 being exploited?

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

Public exploit code:

- Wireless Repeater BE126 - Remote Code Execution (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2017-8771](https://insights.sbomify.com/CVE-2017-8771/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2017-8772](https://insights.sbomify.com/CVE-2017-8772/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2017-8770](https://insights.sbomify.com/CVE-2017-8770/): Path traversal in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-13713 and fix it if it is affected.

What it is: CVE-2017-13713 is a high-severity command injection vulnerability in n/a, published on 7 Sep 2017. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-13713 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-2017-13713/ (Markdown: https://insights.sbomify.com/CVE-2017-13713/index.md)
```

## Sources

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

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