# CVE-2013-20007: Linksys WAG200G through 1.01.06 OS Command Injection via timer_interval in setup.cgi


- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 28 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-c6xm-fp38-v723

## What is CVE-2013-20007?

CVE-2013-20007 is a high-severity vulnerability in Linksys WAG200G, published on 28 Oct 2026. 

### Official description

Linksys WAG200G through 1.01.06 contains an OS command injection vulnerability that allows authenticated attackers to execute commands by injecting backtick-delimited input into the timer_interval parameter. Attackers can send a crafted POST request to setup.cgi to start telnetd or download and run a backdoor, gaining full device control.

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

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


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

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

## Is CVE-2013-20007 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2013-20007 is a high-severity vulnerability in Linksys WAG200G, published on 28 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2013-20007 in the wild and no public exploit code.

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

## Sources

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

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