ControlID iDSecure On-premises up to 4.7.48.0 improper authentication

Summaryinfo

A vulnerability was found in ControlID iDSecure On-premises up to 4.7.48.0. It has been classified as critical. This issue affects some unknown processing. This manipulation causes improper authentication. This vulnerability is handled as CVE-2025-49851. The attack can be initiated remotely. There is not any exploit available.

Detailsinfo

A vulnerability was found in ControlID iDSecure On-premises up to 4.7.48.0. It has been declared as critical. Affected by this vulnerability is an unknown code block. The manipulation with an unknown input leads to a improper authentication vulnerability. The CWE definition for the vulnerability is CWE-287. When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

ControlID iDSecure On-premises versions 4.7.48.0 and prior are vulnerable to an Improper Authentication vulnerability which could allow an attacker to bypass authentication and gain permissions in the product.

The weakness was released with Claroty Team82 as icsa-25-175-05. The advisory is shared at cisa.gov. This vulnerability is known as CVE-2025-49851 since 06/11/2025. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available.

The vulnerability scanner Nessus provides a plugin with the ID 310722 (Control iD iDSecure Improper Authentication (CVE-2025-49851)), which helps to determine the existence of the flaw in a target environment.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the databases at Tenable (310722) and EUVD (EUVD-2025-19062). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

• ControlID

Name

• iDSecure On-premises

Version

• 4.7.0
• 4.7.1
• 4.7.2
• 4.7.3
• 4.7.4
• 4.7.5
• 4.7.6
• 4.7.7
• 4.7.8
• 4.7.9
• 4.7.10
• 4.7.11
• 4.7.12
• 4.7.13
• 4.7.14
• 4.7.15
• 4.7.16
• 4.7.17
• 4.7.18
• 4.7.19
• 4.7.20
• 4.7.21
• 4.7.22
• 4.7.23
• 4.7.24
• 4.7.25
• 4.7.26
• 4.7.27
• 4.7.28
• 4.7.29
• 4.7.30
• 4.7.31
• 4.7.32
• 4.7.33
• 4.7.34
• 4.7.35
• 4.7.36
• 4.7.37
• 4.7.38
• 4.7.39
• 4.7.40
• 4.7.41
• 4.7.42
• 4.7.43
• 4.7.44
• 4.7.45
• 4.7.46
• 4.7.47
• 4.7.48.0

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion