CVE-2024-55019
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 · uneditedIncorrect access control in the component download_wb.cgi of Weintek cMT-3072XH2 easyweb Web Version v2.1.53, OS v20231011 allows unauthenticated attack to download arbitrary files.
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 download_wb.cgi component in Weintek cMT-3072XH2 easyweb Web Version v2.1.53 contains incorrect access control that allows unauthenticated attackers to download arbitrary files from the device's file system via path traversal.
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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Easyweb versionAccess the web interface login page and check the version footer, or check the firmware version in the system settings of the cMT-3072XH2 device. The affected version is 2.1.53.Affected if The installed Easyweb version is 2.1.53, or the firmware date is 20231011.
-
Confirm download_wb.cgi endpoint existsAttempt to access the URI /cgi-bin/download_wb.cgi on the HMI web server. This is the vulnerable CGI component.Affected if The download_wb.cgi endpoint responds (even with an error) indicating it exists on the device.
-
Verify unauthenticated access is possibleCheck whether the web interface allows access to download_wb.cgi without requiring login credentials. This can be confirmed by making a request without session cookies or authentication headers and observing if the CGI executes.Affected if The download_wb.cgi endpoint is reachable and processes requests without requiring authentication.
-
Check network exposureDetermine if the HMI web interface (typically ports 80 or 443) is directly accessible from untrusted networks such as the internet or general corporate networks, rather than being restricted to a management VLAN.Affected if The web interface is exposed to untrusted networks without firewall or network segmentation controls.
You are affected if your device runs Easyweb version 2.1.53 or firmware dated 20231011, the download_wb.cgi endpoint is accessible, and it can be reached without authentication from an untrusted network.
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 patch when available; meanwhile, restrict network access to the HMI web interface using firewall rules or network segmentation to prevent unauthenticated access.
- Consultation4.0 h
- Implementation6.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 $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-55019 — 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-55019 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