dbcve.org
Cmt Svr 100 FirmwareOperating system · Weintek

CVE-2021-27446

CRITICAL · 9.8 CVSS v3.1 Published 2022-05-16
Fix available
A fix is available. Upgrade to 20210209 / 20210222 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
The Weintek cMT product line is vulnerable to code injection, which may allow an unauthenticated remote attacker to execute commands with root privileges on the operation 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 confidence

The Weintek cMT HMI product line contains a code injection vulnerability that allows unauthenticated remote attackers to execute arbitrary commands with root privileges on the underlying Linux-based operating system.

MitigationApply the vendor-supplied firmware update to all affected cMT devices immediately. If patching is not immediately feasible, isolate affected devices on a restricted network segment and disable external access to reduce exposure.

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
Cmt Svr 100 FirmwareOperating system
Affected:< 20210305
Cmt Svr 102 FirmwareOperating system
Affected:< 20210305
Cmt Svr 200 FirmwareOperating system
Affected:< 20210305
Cmt Svr 202 FirmwareOperating system
Affected:< 20210305
Cmt G01 FirmwareOperating system
Affected:< 20210209
Cmt G02 FirmwareOperating system
Affected:< 20210209
Cmt G03 FirmwareOperating system
Affected:< 20210222
Cmt G04 FirmwareOperating system
Affected:< 20210222

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 the device model
    Access the device web interface or check the physical device label to confirm it is a Weintek cMT HMI model (Cmt Svr 100, 102, 200, 202, G01, G02, G03, or G04)
    Affected if The device is one of the listed Weintek cMT models
  2. Determine the firmware version
    Log into the cMT device web interface and navigate to System Settings > System Information to view the installed firmware version
    Affected if The firmware version is earlier than 20210305 for Cmt Svr models, earlier than 20210209 for Cmt G01/G02, or earlier than 20210222 for Cmt G03/G04
  3. Check network exposure
    Verify whether the cMT device web interface (typically port 80/443) is accessible from untrusted networks or the internet
    Affected if The device management interface is reachable from outside the local network without firewall protection

The environment is affected if a Weintek cMT HMI device is running firmware versions below the specified thresholds and is network accessible.

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.

dbcve · scoped
Upgrade available Upgrade to 20210209 / 20210222 / 20210305 or later
Fixed in 202102092021022220210305
Interim mitigation

Apply the vendor-supplied firmware update to all affected cMT devices immediately. If patching is not immediately feasible, isolate affected devices on a restricted network segment and disable external access to reduce exposure.

Recommended fix High confidence

Firmware version >= 20210305 for Cmt Svr series; >= 20210209 for Cmt G01/G02; >= 20210222 for Cmt G03/G04

  1. 1. Identify the specific cMT device model (Cmt Svr 100, 102, 200, 202, G01, G02, G03, or G04) from the affected product list
  2. 2. Determine the current firmware version installed on the device
  3. 3. Download the appropriate updated firmware from the official Weintek download site (dl.weintek.com) - look for firmware dated 20210305 or later for Svr series, 20210209 or later for G01/G02, and 20210222 or later for G03/G04
  4. 4. Follow Weintek's standard firmware update procedure (typically via the device's web interface or dedicated update utility)
  5. 5. After updating, verify the new firmware version is installed and confirm the device is operational
  6. 6. Ensure the device is not directly exposed to the internet (place behind a firewall/NAT) as an additional security measure
Caveat Review Weintek release notes for any functional changes between your current version and the updated firmware; test in a non-production environment first if possible

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Cmt Svr 100 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,360
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-27446 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2021-27446 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