dbcve.org
Zkbio WdmsApplication · Zkteco

CVE-2024-22988

CRITICAL · 9.8 CVSS v3.1 Published 2024-02-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
ZKteco ZKBio WDMS before 9.0.2 Build 20250526 allows an attacker to download a database backup via the /files/backup/ component because the filename is based on a predictable timestamp.

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 confidence

ZKBio WDMS versions before 9.0.2 Build 20250526 expose database backups through the /files/backup/ endpoint using predictable timestamp-based filenames, allowing unauthenticated attackers to download sensitive database backups containing user credentials and biometric data.

MitigationUpdate to ZKBio WDMS version 9.0.2 Build 20250526 or later; alternatively, implement access controls or authentication on the /files/backup/ directory to prevent unauthorized access.

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
Zkbio WdmsApplication
Affected:= 8.0.5

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

Work through these to decide whether this CVE applies to you.

  1. Identify installed ZKBio WDMS version
    Access the ZKBio WDMS admin interface and navigate to System > About, or check the version displayed on the login page. Alternatively, check any version information in the application header or footer.
    Affected if The installed version is 8.0.5 or any version before 9.0.2 Build 20250526. Note: The only explicitly listed affected version is 8.0.5.
  2. Verify backup endpoint exposure
    Attempt to access http://<your-server>/files/backup/ via a web browser or curl command without providing any authentication credentials.
    Affected if The endpoint returns a directory listing or allows access to backup files without requiring login or authentication.
  3. Check for predictable backup files
    Enumerate the /files/backup/ directory for .zip, .sql, .bak, or similar database backup files. Look for files with timestamp-based naming patterns such as backup_YYYYMMDD_HHMMSS.zip or similar.
    Affected if Backup files are present and downloadable, especially if filenames follow a predictable timestamp pattern.
  4. Confirm backup contains sensitive data
    Download a sample backup file (if accessible) and verify it contains user credentials, biometric templates, or other sensitive information typical of a ZKBio WDMS database.
    Affected if The backup file contains plaintext or weakly protected user credentials, biometric data, or other sensitive system information.

You are affected if your ZKBio WDMS installation is version 8.0.5 or earlier (before 9.0.2 Build 20250526) AND the /files/backup/ endpoint is accessible without authentication, as the vulnerability allows unauthenticated download of database backups.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to ZKBio WDMS version 9.0.2 Build 20250526 or later; alternatively, implement access controls or authentication on the /files/backup/ directory to prevent unauthorized access.

Recommended fix Moderate confidence

ZKBio WDMS 9.0.2 Build 20250526 or later

  1. 1. Identify the current installed version of ZKBio WDMS by accessing the admin interface or checking system information.
  2. 2. Contact Zkteco official support or visit the official Zkteco website (www.zkteco.com) to obtain the official patch or upgrade to version 9.0.2 (Build 20250526) or later.
  3. 3. Before applying the upgrade, perform a complete backup of the current system configuration and database.
  4. 4. Apply the upgrade to ZKBio WDMS version 9.0.2 Build 20250526 or the latest stable release available from Zkteco.
  5. 5. After upgrade, verify the /files/backup/ endpoint is no longer accessible without proper authentication and that backup filenames are no longer predictable (timestamp-based).
  6. 6. Change all default credentials and review access controls after the upgrade.
Caveat Review release notes for any breaking changes between 8.x and 9.x branches; ensure compatibility with connected devices and integrations before production deployment

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

Fix this in Zkbio Wdms Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,140
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,024.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-22988 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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