Cm5100 FirmwareOperating system · Skyworthdigital

CVE-2023-51726

MEDIUM · 5.4 CVSS v3.1 Published 2024-01-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
This vulnerability exist in Skyworth Router CM5100, version 4.1.1.24, due to insufficient validation of user supplied input for the SMTP Server Name 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 confidence

Stored XSS vulnerability in Skyworth Router CM5100 (v4.1.1.24) web interface. The SMTP Server Name parameter lacks proper input validation, allowing malicious scripts to be injected and persisted.

MitigationImplement strict input validation and output encoding for the SMTP Server Name parameter. Restrict web interface access to trusted users until vendor patch is applied.

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
Cm5100 FirmwareOperating system
Affected:= 4.1.1.24

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify device model and firmware version
    Access the router web interface or check the administration page for device information. Look for 'CM5100' in the model name and '4.1.1.24' in the firmware version field.
    Affected if The device is a Skyworth CM5100 and the firmware version is exactly 4.1.1.24
  2. Locate SMTP configuration in the web interface
    Navigate to the router web interface and find the email/SMTP settings section. This is typically under 'Advanced Settings', 'Network Settings', or 'Administration' menus.
    Affected if SMTP configuration menu exists and is accessible in the web interface
  3. Check if SMTP Server Name field is present
    In the SMTP settings section, identify the input field for 'SMTP Server' or 'SMTP Server Name' where the mail server address is configured.
    Affected if The SMTP Server Name input field exists and accepts user-supplied values
  4. Verify web interface is accessible without authentication bypass
    Confirm that the router web interface login is functional and you can access the SMTP configuration area with proper admin credentials.
    Affected if The web interface is accessible and SMTP settings can be viewed or modified by an authenticated user
  5. Inspect current SMTP Server Name value for special characters
    Examine the current value stored in the SMTP Server Name field. Look for any HTML or script tags like <script>, javascript:, or other suspicious characters that may indicate stored XSS.
    Affected if The SMTP Server Name field contains or allows storage of HTML/script tags without sanitization

You are affected if you have a Skyworth CM5100 router running firmware version 4.1.1.24 with an accessible web interface that contains an SMTP Server Name configuration field.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation and output encoding for the SMTP Server Name parameter. Restrict web interface access to trusted users until vendor patch is applied.

Fix this in Cm5100 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-51726 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-51726 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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