# CVE-2025-49853: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in ControlID iDSecure On-premises

> Attackers can exploit SQL injection in ControlID iDSecure to leak information and modify database queries, requiring immediate patching.

- **Severity:** Critical 9.3 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Jun 2025
- **Updated:** 27 Jun 2025
- **Also known as:** GHSA-3pcg-mr9h-79cf

## What is CVE-2025-49853?

CVE-2025-49853 is a critical SQL injection vulnerability in ControlID iDSecure On-premises, published on 24 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2025-49853?

It affects 1 product.


Products: Assaabloy Control Id Idsecure.

## How do I fix CVE-2025-49853?

No fix has been published for CVE-2025-49853 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-49853 being exploited?

There is no known exploitation of CVE-2025-49853 in the wild and no public exploit code.

## Other vulnerabilities in ControlID iDSecure On-premises

- [CVE-2023-33367](https://insights.sbomify.com/CVE-2023-33367/): SQL injection in n/a (critical 9.8)
- [CVE-2023-33371](https://insights.sbomify.com/CVE-2023-33371/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2023-33369](https://insights.sbomify.com/CVE-2023-33369/): Path traversal in n/a (critical 9.1)
- [CVE-2025-49851](https://insights.sbomify.com/CVE-2025-49851/): Improper Authentication in ControlID iDSecure On-premises (high 8.7)
- [CVE-2025-49852](https://insights.sbomify.com/CVE-2025-49852/): Server-Side Request Forgery (SSRF) in ControlID iDSecure On-premises (high 8.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-49853 and fix it if it is affected.

What it is: CVE-2025-49853 is a critical SQL injection vulnerability in ControlID iDSecure On-premises, published on 24 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-49853 in the wild and no public exploit code.

Affected product: ControlID iDSecure On-premises. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-49853/ (Markdown: https://insights.sbomify.com/CVE-2025-49853/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-49853
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-49853
- OSV: https://osv.dev/vulnerability/CVE-2025-49853

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-49853/
Summaries are generated and may contain mistakes; the official description above is the record.