LiveActive security incident?Get immediate response
CVE Record

CVE-2022-36635: ZKteco ZKBioSecurity V5000 4.1.3 was discovered to contain a SQL injection vulnerability via the component...

ZKteco ZKBioSecurity V5000 4.1.3 was discovered to contain a SQL injection vulnerability via the component /baseOpLog.do.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2022-36635 is a reported SQL injection in ZKteco ZKBioSecurity V5000 4.1.3. In business terms, a vulnerable access-control or biometric security management system could expose sensitive data or support deeper system compromise. The source bundle does not provide CVSS scoring, vendor remediation details, or evidence of active exploitation.

Executive priority

Treat this as a high-priority exposure review for any ZKBioSecurity V5000 4.1.3 deployment, especially internet-facing systems. Business urgency depends on reachability and whether vendor remediation is available.

Technical view

The CVE description identifies SQL injection through the /baseOpLog.do component in ZKteco ZKBioSecurity V5000 4.1.3. The only included third-party reference title describes SQL injection leading to RCE, but the bundle does not include exploit details, patch status, CVSS metrics, or affected version ranges beyond 4.1.3.

Likely exposure

Exposure is most likely where ZKteco ZKBioSecurity V5000 4.1.3 is deployed and the application interface, including /baseOpLog.do, is reachable by untrusted users or networks.

Exploitation context

CISA KEV status is false in the provided bundle. The referenced article title indicates a SQL injection-to-RCE path, but the bundle does not establish active exploitation, exploit maturity, authentication requirements, or reliable public remediation details.

Researcher notes

Evidence is limited to the CVE record and one public reference. The affected product is named in the description, while structured affected fields are not populated. Avoid assuming broader ZKBioSecurity versions without vendor confirmation.

Mitigation direction

  • Check ZKteco guidance for fixed versions or supported upgrade paths.
  • Restrict ZKBioSecurity access to trusted administrative networks only.
  • Place the interface behind VPN, SSO, or network allowlists where possible.
  • Review application and database logs for suspicious /baseOpLog.do activity.
  • Prioritize backup, credential review, and incident checks for exposed deployments.

Validation and detection

  • Inventory ZKBioSecurity deployments and confirm exact version numbers.
  • Determine whether /baseOpLog.do is reachable from untrusted networks.
  • Check whether the system is internet-facing or accessible through partner networks.
  • Review logs around the application and database for anomalous query behavior.
  • Confirm whether vendor advisories or updates exist for the installed version.
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.

description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-36635 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

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

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

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

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