dbcve.org
Cmt Fhd FirmwareOperating system · Weintek

CVE-2023-40145

HIGH · 8.8 CVSS v3.1 Published 2023-10-19
Fix available
A fix is available. Upgrade to 20210206 / 20210212 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
In Weintek's cMT3000 HMI Web CGI device, an anonymous attacker can execute arbitrary commands after login to the device.

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

Weintek cMT3000 HMI Web CGI device contains a command injection vulnerability where an authenticated attacker can execute arbitrary commands on the underlying operating system, likely due to insufficient input validation in the web CGI interface.

MitigationRestrict network access to the HMI management interface, enforce strong authentication credentials, apply any vendor-supplied patches, and consider network segmentation for industrial control systems.

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 Fhd FirmwareOperating system
Affected:< 20210212
Cmt Hdm FirmwareOperating system
Affected:< 20210206
Cmt3071 FirmwareOperating system
Affected:< 20210220
Cmt3072 FirmwareOperating system
Affected:< 20210220
Cmt3090 FirmwareOperating system
Affected:< 20210220
Cmt3103 FirmwareOperating system
Affected:< 20210220
Cmt3151 FirmwareOperating system
Affected:< 20210220

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

CVSS:3.1/AV:N/AC:L/PR:L/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 Weintek cMT model
    Access the device web interface or check the physical device label to confirm the exact model number (e.g., cMT3071, cMT3103, cMT3151, etc.)
    Affected if The device is a Weintek cMT3000 series HMI (Cmt Fhd, Cmt Hdm, Cmt3071, Cmt3072, Cmt3090, Cmt3103, or Cmt3151)
  2. Check the firmware version
    Log into the HMI web interface and navigate to System Settings > Firmware Information, or access the device via Weintek EasyBuilder Pro software to view the firmware version
    Affected if The firmware version is below 20210212 for Cmt Fhd, below 20210206 for Cmt Hdm, or below 20210220 for cMT3071/3072/3090/3103/3151 models
  3. Verify Web CGI interface accessibility
    Attempt to access the CGI endpoint on the device (e.g., http://[device-ip]/cgi-bin/ or similar web CGI paths) using a web browser
    Affected if The web CGI interface is reachable and responds to requests
  4. Confirm authentication is required
    Try to access privileged CGI functions without logging in, or check if the authentication session can be bypassed
    Affected if The CGI interface accepts authentication or default credentials are still in use

The environment is affected if the device is a Weintek cMT3000 series HMI running firmware versions below the thresholds (20210212, 20210206, or 20210220 depending on model) AND the web CGI interface is accessible with valid credentials.

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 20210206 / 20210212 / 20210220 or later
Fixed in 202102062021021220210220
Interim mitigation

Restrict network access to the HMI management interface, enforce strong authentication credentials, apply any vendor-supplied patches, and consider network segmentation for industrial control systems.

Recommended fix Moderate confidence

Firmware versions released on or after 2021-02-20 (specific to each model as listed in the affected versions)

  1. 1. Identify the exact Cmt model of your Weintek HMI device by checking the device label or web interface
  2. 2. Download the latest firmware for your specific model from the official Weintek download site (dl.weintek.com)
  3. 3. Ensure the firmware version date is equal to or later than the threshold for your model: Cmt Fhd >= 20210212, Cmt Hdm >= 20210206, Cmt3071/Cmt3072/Cmt3090/Cmt3103/Cmt3151 >= 20210220
  4. 4. Backup your current HMI project and configuration
  5. 5. Access the HMI web interface or use EasyBuilder Pro to update the firmware
  6. 6. After upgrade, verify the command injection vulnerability is resolved by confirming the patch is applied
Caveat Review Weintek release notes for any functionality changes between your current firmware version and the upgrade version; backup projects before upgrading

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

Fix this in Cmt Fhd Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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