Skip to main content
VulnerabilityPublished Updated

CVE-2025-49853: ControlID iDSecure On-premises · SQL Injection

Affects ControlID iDSecure On-premisesSource CVE Database V5

0

Not known to be exploited · CVSS 9.3 Critical.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 4.0 base score
9.3Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 41% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Jun 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
ControlID iDSecure On-premisesAffected
  • =0
Fixed in–

AI-suggested

Given the lack of an official patch at the time of disclosure, European organizations should implement the following specific mitigation measures: 1) Immediately restrict network access to the iDSecure On-premises management interfaces by implementing strict firewall rules and network segmentation, ensuring only trusted administrative hosts can communicate with the system. 2) Deploy Web Application Firewalls (WAFs) or intrusion prevention systems (IPS) with custom rules to detect and block common SQL injection payloads targeting the iDSecure application. 3) Conduct thorough input validation and sanitization on any custom integrations or scripts interacting with iDSecure databases, if applicable. 4) Monitor database query logs and application logs for anomalous or unexpected SQL queries that may indicate exploitation attempts. 5) Enforce the principle of least privilege on database accounts used by iDSecure, limiting their permissions to only necessary operations to reduce potential damage from injection attacks. 6) Prepare for rapid deployment of vendor patches by maintaining up-to-date asset inventories and testing environments. 7) Educate security and IT teams about this vulnerability to enhance detection and response capabilities. These targeted actions go beyond generic advice by focusing on network-level controls, monitoring, and privilege restrictions tailored to the specific product and vulnerability characteristics.

Description

ControlID iDSecure On-premises versions 4.7.48.0 and prior are vulnerable to SQL injections which could allow an attacker to leak arbitrary information and insert arbitrary SQL syntax into SQL queries.

References

Community reviews

Loading reviews…