Zmm200 FirmwareOperating system · Zkteco

CVE-2022-42953

HIGH · 7.5 CVSS v3.1 Published 2022-12-25
Fix available
A fix is available. Upgrade to 8.88 / 15.00 or later.
See remediation →
84/100
Remediation priority · High
Public exploit Remotely reachable No privileges 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
Certain ZKTeco products (ZEM500-510-560-760, ZEM600-800, ZEM720, ZMM) allow access to sensitive information via direct requests for the form/DataApp?style=1 and form/DataApp?style=0 URLs. The affected versions may be before 8.88 (ZEM500-510-560-760, ZEM600-800, ZEM720) and 15.00 (ZMM200-220-210). The fixed versions are firmware version 8.88 (ZEM500-510-560-760, ZEM600-800, ZEM720) and firmware version 15.00 (ZMM200-220-210).

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

A detailed technical summary for this CVE is being prepared.

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
Zmm200 FirmwareOperating system
Affected:< 15.00
Zmm210 FirmwareOperating system
Affected:< 15.00
Zmm220 FirmwareOperating system
Affected:< 15.00
Zem720 FirmwareOperating system
Affected:< 8.88
Zem600 FirmwareOperating system
Affected:< 8.88
Zem800 FirmwareOperating system
Affected:< 8.88
Zem510 FirmwareOperating system
Affected:< 8.88
Zem560 FirmwareOperating system
Affected:< 8.88

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
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

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 8.88 / 15.00 or later
Fixed in 8.8815.00
Recommended fix High confidence

ZMM200/210/220 to firmware 15.00; Zem720/600/800/510/560 to firmware 8.88

  1. 1. Identify the exact model number (ZMM200, ZMM210, ZMM220, Zem720, Zem600, Zem800, Zem510, or Zem560) of the affected ZKTeco device
  2. 2. Obtain the appropriate firmware update from the official ZKTeco support website or contact ZKTeco technical support
  3. 3. Review the firmware release notes to confirm the update addresses CVE-2022-42953
  4. 4. Back up current device configuration if supported
  5. 5. Upload and install firmware version 15.00 for ZMM200/ZMM210/ZMM220 devices, or firmware version 8.88 for Zem720/Zem600/Zem800/Zem510/Zem560 devices
  6. 6. After reboot, verify the device is running the updated firmware version
  7. 7. Test that the form/DataApp?style=0 and form/DataApp?style=1 endpoints no longer return sensitive information without authentication
Caveat Review release notes for any functionality changes between current and target firmware versions; some legacy features may be deprecated

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-42953 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-42953 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