LiveActive security incident?Get immediate response
CVE Record

CVE-2023-51141: An issue in ZKTeko BioTime v.8.5.4 and before allows a remote attacker to obtain sensitive information via...

An issue in ZKTeko BioTime v.8.5.4 and before allows a remote attacker to obtain sensitive information via the Authentication & Authorization component

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

BioTime versions 8.5.4 and earlier are reported to allow a remote, low-privileged user to obtain sensitive information through an authorization weakness. The main business risk is confidentiality loss, not service disruption. Source data is limited and does not name a vendor patch.

Executive priority

Treat as a moderate confidentiality risk. Prioritize exposed or broadly accessible BioTime instances, then confirm vendor remediation because the source bundle does not provide a named patch.

Technical view

CVE-2023-51141 is mapped to CWE-639 and scored CVSS 6.5: network reachable, low complexity, low privileges required, no user interaction, high confidentiality impact, no integrity or availability impact. The CVE record names the Authentication & Authorization component but provides limited affected-product metadata.

Likely exposure

Organizations using ZKTeko BioTime v8.5.4 or earlier may be exposed, especially if the application is reachable from untrusted networks. The structured affected-product fields are incomplete and list vendor/product as n/a.

Exploitation context

The bundle does not show CISA KEV listing or other evidence of active exploitation. CVSS indicates exploitation requires some authenticated access, so risk increases where many users have accounts or access controls are weak.

Researcher notes

Evidence is sparse: the CVE names BioTime v8.5.4 and before, CWE-639, and the Authentication & Authorization component, but lacks CPEs, detailed affected builds, and remediation data. Avoid assuming exploit maturity from the public gist alone.

Mitigation direction

  • Identify all BioTime deployments and confirm exact versions.
  • Check vendor guidance for fixed versions or official mitigations.
  • Restrict BioTime access to trusted networks or VPN users.
  • Review user roles and remove unnecessary low-privilege accounts.
  • Monitor for unusual authenticated access to sensitive records.

Validation and detection

  • Confirm whether any instance runs BioTime v8.5.4 or earlier.
  • Verify the application is not exposed directly to the internet.
  • Review access-control tests for cross-user or cross-tenant data access.
  • Check logs for unusual authenticated data reads.
  • Document compensating controls if no vendor fix is available.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-639: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-51141 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.5 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
2ADP providers
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N2.83.6CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

6.5Medium
CVSS 3.1 vector shape for CVE-2023-51141Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-639 · source CWE mapping

Authorization Bypass Through User-Controlled Key

Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.