CVE-2023-51719
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 · uneditedThis vulnerability exist in Skyworth Router CM5100, version 4.1.1.24, due to insufficient validation of user supplied input for the Traceroute parameter at its web interface. A remote attacker could exploit this vulnerability by supplying specially crafted input to the parameter at the web interface of the vulnerable targeted system. Successful exploitation of this vulnerability could allow the attacker to perform stored XSS attacks on the targeted system.
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 · moderate confidenceThis is a stored XSS vulnerability in the Skyworth Router CM5100 (version 4.1.1.24) web interface. The Traceroute parameter lacks proper input validation, allowing attackers to inject malicious JavaScript that persists on the device and executes when other users access the 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= 4.1.1.24CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 the device modelAccess the router web interface and check the device information page, or use nmap or SNMP to probe the device for model identification strings (such as 'Skyworth', 'CM5100', or 'Skyworthdigital').Affected if The device is not a Skyworth CM5100 router.
-
Check the firmware versionIn the router web interface, navigate to the Status or System Information page to view the firmware version. Alternatively, check via the administration interface or by querying the device's HTTP response headers or specific endpoints that expose version information.Affected if The firmware version is not exactly 4.1.1.24.
-
Verify the web interface is accessibleAttempt to access the router's HTTP/HTTPS web interface (typically on ports 80 or 443) from a browser or curl command.Affected if The web interface is not accessible or the device does not have a web management interface.
-
Locate the Traceroute featureNavigate through the router web interface menus to find the Traceroute or Network Diagnostics section. Look for a page containing a traceroute input field, often found under Advanced Settings, Network Tools, or Diagnostics.Affected if The Traceroute feature is not present or accessible in the web interface.
-
Inspect the Traceroute parameter for malicious scriptsView the HTML source of the Traceroute page, or use browser developer tools to inspect the input field name and value. Check if the parameter persists across page reloads or if unsanitized script tags appear in the page source.Affected if The Traceroute input field accepts and stores unsanitized HTML or JavaScript (such as <script> tags or event handlers like onerror/onload).
If the device is a Skyworth CM5100 running firmware 4.1.1.24 with an accessible web interface that includes the Traceroute feature, the environment is affected by this stored XSS vulnerability.
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.
From vendor dataUpdate to a patched firmware version if available. If no patch exists, implement input sanitization on the Traceroute parameter or disable the Traceroute functionality until a fix is released.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-51719 — 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-51719 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