CVE-2023-51735
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 Pre-shared key 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 · high confidenceA stored XSS vulnerability exists in Skyworth Router CM5100 version 4.1.1.24 web interface. The Pre-shared key parameter fails to properly validate or sanitize user-supplied input, allowing an attacker to inject malicious JavaScript that persists on the page and executes when viewed by other users.
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 router model and firmware versionLog into the router web interface (typically 192.168.1.1 or 192.168.0.1) and navigate to Status or System Settings to view the firmware version. Alternatively, check the label on the device or documentation for model CM5100 and version 4.1.1.24.Affected if The device is a Skyworth CM5100 running firmware version 4.1.1.24.
-
Locate the Pre-shared key configuration pageIn the router web interface, navigate to Wireless Settings or Wireless Security section where WPA/WPA2 pre-shared key (PSK) is configured.Affected if The wireless security configuration page with Pre-shared key input field is accessible.
-
Test input sanitization on the Pre-shared key fieldEnter a test payload such as <script>alert('XSS')</script> or <img src=x onerror=alert(1)> into the Pre-shared key field and save the configuration. Then reload the page or view the wireless settings again.Affected if The injected script tags or event handlers are rendered as-is in the page HTML without encoding, indicating lack of input sanitization.
-
Verify persistence of the injected scriptAfter saving, log out of the router admin panel, log back in, and navigate back to the wireless security page to see if the injected payload persists and executes.Affected if The malicious payload persists in the configuration and executes when the page loads, confirming a stored XSS vulnerability.
If the device is a Skyworth CM5100 on firmware 4.1.1.24 and the Pre-shared key field accepts and renders unsanitized HTML/JavaScript, the environment is affected by CVE-2023-51735.
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 dataImplement proper input validation and output encoding for the Pre-shared key parameter to neutralize malicious script content. Apply vendor security patches when available.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-51735 — 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-51735 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