CVE-2024-55022
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 · uneditedWeintek cMT-3072XH2 easyweb v2.1.53, OS v20231011 was discovered to contain an authenticated command injection vulnerability via the HMI Name parameter.
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 confidenceAuthenticated command injection vulnerability in Weintek cMT-3072XH2 easyweb v2.1.53 allows remote attackers with valid credentials to execute arbitrary operating system commands through the HMI Name parameter. The vulnerability stems from insufficient input sanitization, enabling attackers to inject shell commands that are executed with the privileges of the web server process.
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= 2.1.53= 20231011CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the HMI device modelAccess the device system information or check the physical device label to confirm the model is cMT-3072XH2Affected if The device is a Weintek cMT-3072XH2 model
-
Check the firmware versionLog into the device web interface or use the device's system info page to view the firmware build date/version. Compare against 20231011Affected if Firmware version equals 20231011 exactly
-
Check the Easyweb versionLocate the Easyweb software version in the device web interface (typically under System Settings or About). Compare against 2.1.53Affected if Easyweb version is 2.1.53 exactly
-
Verify remote web management is enabledCheck the device network settings to confirm the web interface is accessible over the network (look for HTTP/HTTPS server settings)Affected if The web interface is enabled and accessible remotely
-
Check HMI Name configuration accessNavigate to the HMI settings in the web interface where the HMI Name parameter can be modifiedAffected if The HMI Name parameter is accessible and can be saved
You are affected if you have a Weintek cMT-3072XH2 device running firmware version 20231011 with Easyweb version 2.1.53 and the web interface is accessible with valid credentials.
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 dataRestrict web interface access to trusted IP addresses/networks using network segmentation, apply vendor firmware updates when available, and implement least-privilege accounts for HMI management. If patching is not immediately possible, monitor for unauthorized access and disable remote web management if not required.
- Consultation4.0 h
- Implementation4.0 h
- Testing4.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,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-55022 — 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-2024-55022 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