CVE-2024-55026
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 · uneditedAn issue in the reset_pj.cgi endpoint of Weintek cMT-3072XH2 easyweb v2.1.53, OS v20231011 allows unauthorized attackers to execute arbitrary commands via supplying a crafted GET request.
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 confidenceThe Weintek cMT-3072XH2 HMI running easyweb v2.1.53 contains a command injection vulnerability in the reset_pj.cgi endpoint. Attackers can send specially crafted GET requests with malicious parameters that are improperly sanitized and executed by the underlying operating system, allowing full unauthorized command execution with the privileges of the web service.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the HMI device modelAccess the device web interface or check device labeling to confirm the model is cMT-3072XH2Affected if Device model is Weintek cMT-3072XH2
-
Check easyweb versionLog into the HMI web interface and navigate to System Settings > System Information, or access the easyweb version via the CGI endpoint or login page footerAffected if easyweb version equals 2.1.53
-
Check firmware versionLog into the HMI web interface and navigate to System Settings > System Information to view the firmware build dateAffected if Firmware build date equals 20231011
-
Verify web interface is enabledAttempt to access the device web interface via HTTP/HTTPS on the configured port (typically 80 or 443)Affected if Web interface is accessible and CGI endpoints are enabled
-
Confirm reset_pj.cgi endpoint existsSend a GET request to http://[device-ip]/cgi-bin/reset_pj.cgi and verify the endpoint respondsAffected if The reset_pj.cgi endpoint is present and responds
If the device is a Weintek cMT-3072XH2 with easyweb version 2.1.53 or firmware build 20231011, and the web interface with CGI endpoints is accessible, the environment is affected by this command injection vulnerability.
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 dataApply vendor firmware patches if available; otherwise, restrict network access to the device's web interface using firewall rules or network segmentation, and disable the affected CGI endpoint if possible.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
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 locallyCheck whether your project pulls in CVE-2024-55026 — 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-55026 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