CVE-2025-49851
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedControlID 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceControlID iDSecure On-premises versions 4.7.48.0 and prior contain an improper authentication vulnerability that allows attackers to bypass the authentication mechanism entirely and gain unauthorized access to the product with elevated privileges.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 4.7.50.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify iDSecure installationLocate the iDSecure application on your on-premises server. Check for installed software named 'iDSecure', 'ControlID', or 'Assaabloy Control Id Idsecure' in your system inventory, services panel, or application directory.Affected if iDSecure software is installed on the system
-
Determine installed versionCheck the installed version of iDSecure. This is typically found in the software's About panel, in Windows Add/Remove Programs, in the application installation directory's version info, or via command line using 'idssecure -v' or similar if available.Affected if Unable to determine the version or version is 4.7.48.0 or prior
-
Compare against affected version rangeCompare your installed version number to the affected range: versions prior to 4.7.50.0 are vulnerable. Check the exact version string installed.Affected if Installed version is less than 4.7.50.0
-
Verify authentication interface is exposedConfirm that the iDSecure web interface or API endpoint is accessible from your network. Check if the authentication portal is enabled and reachable.Affected if The authentication interface is enabled and network-accessible
Your environment is affected if iDSecure version 4.7.48.0 or prior is installed and the authentication interface is accessible.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped4.7.50.0
Upgrade iDSecure to a version beyond 4.7.48.0 that addresses the authentication bypass vulnerability. If immediate patching is not possible, implement additional authentication controls such as network segmentation, MFA, or WAF rules to mitigate the risk.
iDSecure version 4.7.50.0 or later
- Verify the current iDSecure version by accessing the admin console or checking system information
- Download iDSecure version 4.7.50.0 or later from the official Control ID vendor portal
- Review upgrade documentation and ensure backup of current configuration is performed
- Apply the upgrade following the vendor's standard upgrade procedure
- After upgrade, verify that authentication is functioning correctly
- Confirm the new version is 4.7.50.0 or higher
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-49851 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-49851 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data