# CVE-2013-4731: Command injection in n/a

> Remote attackers can execute arbitrary commands on the Choice Wireless Green Packet WIXFMR-111 modem via shell metacharacters in the web interface.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Jun 2013
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-52jw-3r26-6gcc

## What is CVE-2013-4731?

CVE-2013-4731 is a critical command injection vulnerability in n/a, published on 29 Jun 2013. It can be exploited over the network, with no action from the victim.

### Official description

ajax.cgi in the web interface on the Choice Wireless Green Packet WIXFMR-111 4G WiMax modem allows remote attackers to execute arbitrary commands via shell metacharacters in the pip parameter in an Ajax tag_ipPing request, a different vulnerability than CVE-2013-3581.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2013-4731?

It affects 1 product.


Products: Choice-Wireless Wixfmr-111.

## How do I fix CVE-2013-4731?

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

## Is CVE-2013-4731 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-4731 and fix it if it is affected.

What it is: CVE-2013-4731 is a critical command injection vulnerability in n/a, published on 29 Jun 2013. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-4731 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-2013-4731/ (Markdown: https://insights.sbomify.com/CVE-2013-4731/index.md)
```

## Sources

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

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