CVE-2025-49853: ControlID iDSecure On-premises versions 4.7.48.0 and prior are vulnerable to SQL injections which could allow

Q: How do I fix CVE-2025-49853?

control id idsecure: upgrade to 4.7.50.0. Exact commands for each OS are on this page.

Q: Is CVE-2025-49853 being exploited?

CVE-2025-49853 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2025-49853 affect?

CVE-2025-49853 affects control id idsecure. Severity is critical (CVSS 9.1). 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.

Q: How urgent is CVE-2025-49853?

Priority 47/100. Critical severity; Remotely exploitable, no login, no user action

This month

CRITICAL 9.1REMOTEUPGRADE

CVE-2025-49853 is a critical-severity flaw (CVSS 9.1) affecting control id idsecure. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

Critical severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	9.1 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.5% (top 59%)
CISA exploited list	No
Weakness	CWE-89
Published	2025-06-24
Last modified	2026-06-17

Publisher (CNA): ICS-CERT · Vendor: assaabloy

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2025-06-24 20:15 UTCPublished CVE record published
2026-06-17 09:32 UTCUpdated Record last modified

assaabloy control id idsecure UPGRADE

Affected: < 4.7.50.0

Fixed in: 4.7.50.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy control-id-idsecure || rpm -q control-id-idsecure || control-id-idsecure --version

2. UPGRADE to 4.7.50.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade control-id-idsecure

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade control-id-idsecure

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-49853?

control id idsecure: upgrade to 4.7.50.0. Exact commands for each OS are on this page.

Is CVE-2025-49853 being exploited?

CVE-2025-49853 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2025-49853 affect?

CVE-2025-49853 affects control id idsecure. Severity is critical (CVSS 9.1). 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.

How urgent is CVE-2025-49853?

Priority 47/100. Critical severity; Remotely exploitable, no login, no user action

Related CVEs

CVE-2025-49852 HIGH 7.5 UPGRADE ControlID iDSecure On-premises versions 4.7.48.0 and prior are vulnerable to a server-side request forgery vul
CVE-2025-49851 CRITICAL 9.8 UPGRADE ControlID iDSecure On-premises versions 4.7.48.0 and prior are vulnerable to an improper authentication vulner

References

← Back to latest CVEs