CVE-2013-20009: Linksys WAG200G stored cross-site scripting in policy_name

CVE-2013-20009 · Severity: medium · CVSS 4.8 · Published 2026-10-28

The Linksys WAG200G is a wireless ADSL home gateway used to connect home networks to the internet. An authenticated attacker can inject malicious JavaScript code into the device's access control policy name, which then executes in the browsers of administrators viewing the wireless status page, potentially allowing session hijacking or credential theft.

Technologies: Linksys WAG200G. Vendors: Linksys.

Quick answers

Is CVE-2013-20009 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2013-20009 being exploited in the wild.
How severe is CVE-2013-20009?
Medium severity, with a CVSS score of 4.8, published 28 October 2026.
Which products and versions are affected?
Linksys WAG200G through 1.01.06.
Is there a fix for CVE-2013-20009?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2013-20009 attacked?
It is attacked over the network, in a network appliance.
Am I affected by CVE-2013-20009?
Check whether you run Linksys WAG200G at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A stored cross-site scripting vulnerability exists in the policy_name parameter of setup.cgi, which fails to properly validate or sanitize user input before storing and displaying it. An authenticated attacker can inject JavaScript via the AccessRes.htm page that persists in the device configuration and executes in administrator browsers when they visit the Status > Wireless page. No patch is available; the vendor closed the case without providing a fix.

Affected products

  • Linksys WAG200G through 1.01.06

Timeline

  • 2013-02-08: disclosed
  • 2012-10: other: Vulnerability discovered

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.