CVE-2023-23313
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCertain 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceMultiple Draytek Vigor router models contain a reflected Cross Site Scripting (XSS) vulnerability in the wlogin.cgi and user_login.cgi scripts of the web application management portal. An attacker can inject malicious JavaScript code through the login scripts that executes in the victim's browser when accessing the router's web interface.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 3.9.4< 3.9.4< 3.9.4< 3.9.4< 3.9.4< 3.9.4< 3.9.4< 3.9.4CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify router modelAccess the router's web interface or check the device label to confirm the exact model number (e.g., Vigor2860, Vigor2860n, Vigor2860n Plus, Vigor2860vn Plus, Vigor2860ac, Vigor2860vac, Vigor2860l, or Vigor2860ln)Affected if The model is any of the Vigor2860 series variants listed as affected
-
Check firmware versionLog into the router web interface and navigate to the System Status or Maintenance section to view the current firmware version, or use the router's command line interface if availableAffected if The firmware version is below 3.9.4 (for example, 3.9.3, 3.9.2, etc.)
-
Verify web management interface accessibilityAttempt to access the router's login page via HTTP/HTTPS from the network segment where the router is deployedAffected if The web interface (wlogin.cgi or user_login.cgi) is reachable over the network
-
Confirm remote access configurationCheck the router's remote management settings (usually under System Maintenance > Remote Access or similar) to determine if web-based management is enabled for external IPs or WAN interfacesAffected if Remote web management access is enabled and the login scripts are exposed to untrusted networks
-
Assess login script exposureAttempt to access the specific endpoints /cgi/wlogin.cgi and /cgi/user_login.cgi on the router's IP address to confirm they respondAffected if Either wlogin.cgi or user_login.cgi returns a response, indicating the vulnerable scripts are accessible
You are affected if you have a Draytek Vigor2860 series router running firmware version below 3.9.4 and the router's web login scripts are accessible on your network.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped3.9.4
Update affected routers to firmware versions that include the security patch from Draytek. If patches are unavailable, consider disabling remote web management access, implementing WAF rules to filter XSS payloads on login parameters, or restricting management interface access to trusted IP addresses.
Vigor2860 series firmware 3.9.4
- 1. Access the Draytek Vigor router web management interface
- 2. Navigate to System Maintenance > Firmware Upgrade
- 3. Download the firmware version 3.9.4 (or latest available) from the official Draytek website (www.draytek.com)
- 4. Upload the firmware file to the router
- 5. Wait for the firmware upgrade process to complete and the router to reboot
- 6. Verify the firmware version has been updated successfully
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-23313 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-23313 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data