# CVE-2013-3307: Command injection in E1000

> Attackers can execute arbitrary OS commands on Linksys routers via the ping_ip parameter, requiring firmware updates to mitigate.

- **Severity:** High 8.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Jul 2025
- **Updated:** 11 Jul 2025
- **Also known as:** GHSA-wg68-f4gp-9q35

## What is CVE-2013-3307?

CVE-2013-3307 is a high-severity command injection vulnerability in Linksys E1000, published on 11 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Linksys E1000 devices through 2.1.02, E1200 devices before 2.0.05, and E3200 devices through 1.0.04 allow OS command injection via shell metacharacters in the apply.cgi ping_ip parameter on TCP port 52000.

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

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


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

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

## Is CVE-2013-3307 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2013-3307 exists.

Public exploit code:

- Linksys X3000 1.0.03 build 001 - Multiple Vulnerabilities (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-3307 is a high-severity command injection vulnerability in Linksys E1000, published on 11 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2013-3307 exists.

Affected product: Linksys E1000. 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-3307/ (Markdown: https://insights.sbomify.com/CVE-2013-3307/index.md)
```

## Sources

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

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