# CVE-2013-5703: Cross-site scripting in n/a

> Remote attackers can execute arbitrary JavaScript and modify router settings via a crafted SSID value in DrayTek Vigor routers.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Oct 2013
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-3pwq-cm7p-cvv5

## What is CVE-2013-5703?

CVE-2013-5703 is a medium-severity cross-site scripting vulnerability in n/a, published on 22 Oct 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The DrayTek Vigor 2700 router 2.8.3 allows remote attackers to execute arbitrary JavaScript code, and modify settings or the DNS cache, via a crafted SSID value that is not properly handled during insertion into the sWlessSurvey value in variables.js.

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

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

It affects 2 products.


Products: Draytek Vigor 2700 Router, Draytek Vigor 2700 Router Firmware.

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

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

## Is CVE-2013-5703 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2013-5703 is a medium-severity cross-site scripting vulnerability in n/a, published on 22 Oct 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-5703 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-5703/ (Markdown: https://insights.sbomify.com/CVE-2013-5703/index.md)
```

## Sources

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

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