dbcve.org
Control Id IdsecureApplication · Assaabloy

CVE-2025-49852

HIGH · 7.5 CVSS v3.1 Published 2025-06-24
Fix available
A fix is available. Upgrade to 4.7.50.0 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
ControlID iDSecure On-premises versions 4.7.48.0 and prior are vulnerable to a server-side request forgery vulnerability which could allow an unauthenticated attacker to retrieve information from other servers.

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 · high confidence

ControlID iDSecure On-premises versions 4.7.48.0 and prior contain a server-side request forgery (SSRF) vulnerability that allows unauthenticated attackers to cause the affected server to make arbitrary requests to internal or external resources, potentially exposing sensitive information from internal services or cloud metadata endpoints.

MitigationUpgrade iDSecure to a version newer than 4.7.48.0 that includes the SSRF fix, or apply any vendor-supplied patch; if upgrade is not immediately possible, restrict the application's ability to make outbound network connections through firewall rules or network segmentation.

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
Control Id IdsecureApplication
Affected:< 4.7.50.0

CVSS 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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify iDSecure version
    Access the iDSecure administrative interface (typically via https://[hostname]/idsecure or similar) and navigate to the About, System Info, or Help section to confirm the installed version number
    Affected if The installed version is 4.7.48.0 or any version prior to 4.7.50.0
  2. Check web portal exposure
    Determine if the iDSecure web interface is accessible from untrusted networks by reviewing firewall rules, reverse proxy configuration, or by performing an external port scan targeting common web ports (80, 443, 8080, 8443)
    Affected if The web portal is exposed to external or untrusted networks, making the SSRF vulnerability exploitable by remote attackers
  3. Confirm outbound network capability
    Review network configuration to determine whether the iDSecure server is permitted to make outbound HTTP/HTTPS connections to arbitrary destinations
    Affected if The server has unrestricted outbound network access, which is required for an SSRF attack to reach internal resources or cloud metadata endpoints

A system is affected if iDSecure version is below 4.7.50.0 and the web interface is network-accessible, allowing unauthenticated attackers to trigger arbitrary server-side requests.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 4.7.50.0 or later
Fixed in 4.7.50.0
Interim mitigation

Upgrade iDSecure to a version newer than 4.7.48.0 that includes the SSRF fix, or apply any vendor-supplied patch; if upgrade is not immediately possible, restrict the application's ability to make outbound network connections through firewall rules or network segmentation.

Recommended fix Moderate confidence

iDSecure version 4.7.50.0 or later

  1. Backup the current iDSecure configuration and database before initiating the upgrade
  2. Review the official iDSecure 4.7.50.0 release notes for any special upgrade requirements or prerequisites
  3. Download the iDSecure version 4.7.50.0 or later from the official Control ID vendor portal
  4. Follow the vendor's documented upgrade procedure for on-premises iDSecure installations
  5. After upgrading, verify that the SSRF vulnerability is remediated by confirming the application functions normally
  6. Test that the fix does not introduce regressions in legitimate functionality

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Control Id Idsecure Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-49852 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-49852 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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