# CVE-2023-23313: Cross-site scripting in n/a

> Attackers can inject malicious scripts into Draytek router web interfaces, potentially compromising user sessions and data.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 3 Mar 2023
- **Updated:** 7 Mar 2025
- **Also known as:** GHSA-86xh-6qhg-p6c2

## What is CVE-2023-23313?

CVE-2023-23313 is a medium-severity cross-site scripting vulnerability in Draytek Vigor3910 Firmware, published on 3 Mar 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Certain Draytek products are vulnerable to Cross Site Scripting (XSS) via the wlogin.cgi script and user_login.cgi script of the router's web application management portal. This affects Vigor3910, Vigor1000B, Vigor2962 v4.3.2.1; Vigor2865 and Vigor2866 v4.4.1.0; Vigor2927 v4.4.2.2; and Vigor2915, Vigor2765, Vigor2766, Vigor2135 v4.4.2.0; Vigor2763 v4.4.2.1; Vigor2862 and Vigor2926 v3.9.9.0; Vigor2925 v3.9.3; Vigor2952 and Vigor3220 v3.9.7.3; Vigor2133 and Vigor2762 v3.9.6.4; and Vigor2832 v3.9.6.2.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2023-23313?

It affects 91 products.


Products: Draytek Vigor1000b Firmware, Draytek Vigor130 Firmware, Draytek Vigor165 Firmware, Draytek Vigor166 Firmware, Draytek Vigor2133 Firmware, Draytek Vigor2133ac Firmware, Draytek Vigor2133fvac Firmware, Draytek Vigor2133n Firmware, Draytek Vigor2133vac Firmware, Draytek Vigor2135 Firmware, Draytek Vigor2135ac Firmware, Draytek Vigor2135ax Firmware, Draytek Vigor2135fvac Firmware, Draytek Vigor2135vac Firmware, Draytek Vigor2762 Firmware, Draytek Vigor2762ac Firmware, Draytek Vigor2762n Firmware, Draytek Vigor2762vac Firmware, Draytek Vigor2763 Firmware, Draytek Vigor2763ac Firmware and 71 more.

## How do I fix CVE-2023-23313?

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

## Is CVE-2023-23313 being exploited?

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

## Other vulnerabilities in Draytek Vigor3910 Firmware

- [CVE-2022-32548](https://insights.sbomify.com/CVE-2022-32548/): Memory corruption in n/a (critical 10.0)
- [CVE-2024-51138](https://insights.sbomify.com/CVE-2024-51138/): Memory corruption in n/a (critical 9.8)
- [CVE-2024-51139](https://insights.sbomify.com/CVE-2024-51139/): Memory corruption in n/a (critical 9.8)
- [CVE-2024-41593](https://insights.sbomify.com/CVE-2024-41593/): Memory corruption in n/a (critical 9.8)
- [CVE-2024-41588](https://insights.sbomify.com/CVE-2024-41588/): Memory corruption in n/a (high 8.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-23313 and fix it if it is affected.

What it is: CVE-2023-23313 is a medium-severity cross-site scripting vulnerability in Draytek Vigor3910 Firmware, published on 3 Mar 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-23313 in the wild and no public exploit code.

Affected product: Draytek Vigor3910 Firmware. 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-2023-23313/ (Markdown: https://insights.sbomify.com/CVE-2023-23313/index.md)
```

## Sources

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

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