CVE-2013-20009 Linksys WAG200G through 1.01.06 Stored XSS via policy_name Parameter
Medium 4.8
Published
Updated
Check this codebase for CVE-2013-20009 and fix it if it is affected.
What it is: CVE-2013-20009 is a medium-severity vulnerability in Linksys WAG200G, published on 28 Oct 2026.
Exploitation: There is no known exploitation of CVE-2013-20009 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-20009/ (Markdown: https://insights.sbomify.com/CVE-2013-20009/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2013-20009?
CVE-2013-20009 is a medium-severity vulnerability in Linksys WAG200G, published on 28 Oct 2026.
Official description
Linksys WAG200G through 1.01.06 contains a stored cross-site scripting vulnerability that allows authenticated attackers to inject scripts via the policy_name parameter in setup.cgi. Attackers can save a malicious policy name from the AccessRes.htm page that executes in administrators' browsers when viewing the Status > Wireless page.
Weakness: CWE-79
Which versions are affected by CVE-2013-20009?
How do I fix CVE-2013-20009?
No fix has been published for CVE-2013-20009 yet. Limit exposure of the affected software until one is available.
Is CVE-2013-20009 being exploited?
There is no known exploitation of CVE-2013-20009 in the wild and no public exploit code.
Sources
Also known as GHSA-x9c2-j44q-2h83.