HIGH · CVSS 7.5 CISA Known Exploited Vulnerability

CVE-2023-38950

ZKTeco BioTime Path Traversal Vulnerability

ZKTeco BioTime

A path traversal vulnerability in the iclock API of ZKTeco BioTime v8.5.5 allows unauthenticated attackers to read arbitrary files via supplying a crafted payload. This vulnerability was fixed in version 9.0.120240617.19506 of ZKBioTime.

CVSS
7.5
HIGH
EPSS
92.5%
30-day exploitation
Ransomware groups
0
recorded exploiting
Published
3 Aug 2023
CWE-22

Exploitation status

CISA Known Exploited Vulnerabilities

Listed by CISA on 19 May 2025. US federal agencies were required to remediate it by 9 June 2025.

EPSS — exploitation probability

FIRST puts the probability of exploitation activity in the next 30 days at 92.5%, which is higher than 99.8% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Frequently asked questions

Is CVE-2023-38950 being exploited by ransomware groups?

No ransomware group in this database is currently recorded as exploiting CVE-2023-38950.

What does CVE-2023-38950 affect?

CVE-2023-38950 affects ZKTeco BioTime. A path traversal vulnerability in the iclock API of ZKTeco BioTime v8.5.5 allows unauthenticated attackers to read arbitrary files via supplying a crafted payload. This vulnerability was fixed in version 9.0.120240617.19506 of ZKBioTime.

How severe is CVE-2023-38950?

CVE-2023-38950 is rated HIGH with a CVSS base score of 7.5. EPSS puts the probability of exploitation in the next 30 days at 92.5%, higher than 99.8% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 9 June 2025.

How should organisations respond to CVE-2023-38950?

Apply the vendor patch for ZKTeco BioTime as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.