Skip to content

Product

Control iD iDSecure vulnerabilities

4 published CVES affecting Control iD iDSecure, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).

Total
4
Critical
1
High
2
Medium
1
Low
0
Unscored
0
CISA KEV
0

Latest Control iD iDSecure CVEs

Newest publication first

  1. CVE-2026-92626 Control iD iDSecure Unauthenticated Denial of Service

    Published
    HighCVSS 7.5 EPSS 0.46%

    Control iD iDSecure versions prior to 4.8.3.0 are affected by an unauthenticated Denial of Service. The /api/dguardintegration/dguardVersion endpoint dereferences DGuard integration login state that may be unset, raising an unhandled null reference exception. The exception is thr...

  2. CVE-2026-92625 Control iD iDSecure Unauthenticated Denial of Service

    Published
    HighCVSS 7.5 EPSS 0.66%

    Control iD iDSecure versions prior to 4.8.3.0 are affected by an unauthenticated Denial of Service. The /api/license/restartService endpoint is reachable without authentication and invokes an internal routine that terminates the iDSecure service process and relaunches it by way o...

  3. CVE-2023-6329 Control iD iDSecure passwordCustom Authentication Bypass

    Published
    CriticalCVSS 9.8 EPSS 65.0% Framework module

    An authentication bypass vulnerability exists in Control iD iDSecure v4.7.32.0. The login routine used by iDS-Core.dll contains a "passwordCustom" option that allows an unauthenticated attacker to compute valid credentials that can be used to bypass authentication and act as an a...

  4. CVE-2023-2044 Control iD iDSecure Dispositivos Page cross site scripting

    Published
    MediumCVSS 6.1 EPSS 0.36%

    A vulnerability has been found in Control iD iDSecure 4.7.29.1 and classified as problematic. This vulnerability affects unknown code of the component Dispositivos Page. The manipulation of the argument IP-DNS leads to cross site scripting. The attack can be initiated remotely. V...

Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.