CVE-2021-27442
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 · uneditedThe Weintek cMT product line is vulnerable to a cross-site scripting vulnerability, which could allow an unauthenticated remote attacker to inject malicious JavaScript code.
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 confidenceThe Weintek cMT product line contains a cross-site scripting (XSS) vulnerability in its web interface. An unauthenticated remote attacker can inject malicious JavaScript code through vulnerable input fields, potentially allowing session hijacking, credential theft, or administrative action execution via the victim's browser.
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< 20210305< 20210305< 20210305< 20210305< 20210209< 20210209< 20210222< 20210222CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 your cMT model numberAccess the device web interface and navigate to System Information, or check the physical device labeling. Look for model identifiers such as cMT Svr 100, cMT Svr 102, cMT Svr 200, cMT Svr 202, cMT G01, cMT G02, cMT G03, or cMT G04.Affected if The model is one of the eight affected variants listed in the CVE.
-
Determine the installed firmware versionIn the cMT web interface, go to System Information or System Settings. The firmware version is typically displayed on the main status page or in the About section. Record the full version string including the date code (for example: 20210215).Affected if The firmware version cannot be determined or is below the threshold for your specific model.
-
Compare your firmware version against the affected rangesMatch your model and version to the CVE thresholds: cMT Svr 100/102/200/202 require version < 20210305; cMT G01/G02 require version < 20210209; cMT G03/G04 require version < 20210222. If your installed version is earlier than these dates, you are running a vulnerable version.Affected if Your installed version is earlier than the threshold date for your specific model.
-
Verify the web interface is enabled and accessibleConfirm that the cMT web server is running and accessible by attempting to reach the device IP address in a web browser. The XSS vulnerability requires the web interface to be exposed for an attacker to inject malicious script through input fields.Affected if The web interface is enabled and reachable on the network.
You are affected if your device is a cMT Svr or cMT G model running firmware version earlier than the threshold date for your specific model and the web interface is accessible.
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.
dbcve · scoped202102092021022220210305
Implement robust input validation and output encoding on all user-supplied data within the cMT web interface. Deploy Content Security Policy (CSP) headers to mitigate XSS execution. Apply any vendor-supplied patches when available.
Firmware version 20210305 (or later) for Cmt Svr series; version 20210209 (or later) for Cmt G01/G02; version 20210222 (or later) for Cmt G03/G04
- 1. Identify the specific cMT device model (Cmt Svr 100, Cmt Svr 102, Cmt Svr 200, Cmt Svr 202, Cmt G01, Cmt G02, Cmt G03, or Cmt G04) that needs remediation.
- 2. Navigate to the official Weintek firmware download portal at dl.weintek.com.
- 3. Locate and download the firmware update for your specific device model: For Cmt Svr 100/102/200/202, use version 20210305 or later; for Cmt G01/G02, use version 20210209 or later; for Cmt G03/G04, use version 20210222 or later.
- 4. Review the firmware upgrade instructions in the Weintek product documentation to understand the update procedure.
- 5. Back up the current device configuration if applicable.
- 6. Apply the firmware update to the affected device using the recommended Weintek upgrade method (typically via the device's web interface or Weintek's utility software).
- 7. Verify that the firmware was successfully applied and the device is functioning correctly.
- 8. Confirm the XSS vulnerability is remediated by testing that the previously vulnerable input fields now properly sanitize or encode user input.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-27442 — 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-2021-27442 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