dbcve.org
Dynamics 365Application · Microsoft

CVE-2025-62206

MEDIUM · 6.5 CVSS v3.1 Published 2025-11-11
Fix available
A fix is available. Upgrade to 9.1.41.07 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Exposure of sensitive information to an unauthorized actor in Microsoft Dynamics 365 (on-premises) allows an unauthorized attacker to disclose information over a network.

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

This is an information disclosure vulnerability in Microsoft Dynamics 365 (on-premises) that allows an unauthorized attacker to access sensitive information over a network. The CVSS 6.5 score indicates a medium-severity issue where confidentiality impact is significant but other impacts (integrity, availability) are not affected.

MitigationApply the latest Microsoft security updates for Dynamics 365 on-premises when available. Until a patch is released, implement network segmentation and least-privilege access controls to limit exposure of the Dynamics 365 environment to unauthorized users.

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
Dynamics 365Application
Affected:>= 9.1, < 9.1.41.07

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Check installed Dynamics 365 version
    Open Dynamics 365 Deployment Manager and view the installed version, or run Get-CrmInstalledProductVersion PowerShell cmdlet to retrieve the exact build number
    Affected if The installed version falls within the range 9.1 to 9.1.41.06 (versions less than 9.1.41.07 are affected)
  2. Verify network accessibility of Dynamics 365 services
    Test whether the Dynamics 365 web services (default ports 5555, 80, 443) are reachable from network segments that should not have access, using telnet or network scanning tools
    Affected if Dynamics 365 endpoints are exposed to untrusted networks or users without proper authentication barriers
  3. Confirm on-premises deployment type
    Verify this is a local Dynamics 365 installation rather than Dynamics 365 (online) - check deployment documentation or confirm the IFD (Internet-Facing Deployment) configuration status
    Affected if The affected environment is an on-premises deployment; the CVE specifically states on-premises is affected
  4. Review authentication and authorization configuration
    Check the claims-based authentication settings and IFD configuration through Dynamics 365 Deployment Manager or PowerShell cmdlets (Get-CrmServer, Get-CrmOrganization)
    Affected if Anonymous or weak authentication is enabled for external-facing Dynamics 365 services, allowing unauthorized information access

You are affected if your on-premises Dynamics 365 version is 9.1 or higher but lower than 9.1.41.07, and the services are accessible over the network to unauthorized users.

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 9.1.41.07 or later
Fixed in 9.1.41.07
Interim mitigation

Apply the latest Microsoft security updates for Dynamics 365 on-premises when available. Until a patch is released, implement network segmentation and least-privilege access controls to limit exposure of the Dynamics 365 environment to unauthorized users.

Recommended fix High confidence

9.1.41.07 or later

  1. 1. Back up the current Microsoft Dynamics 365 database and configuration
  2. 2. Download the Dynamics 365 version 9.1.41.07 or later update from the official Microsoft Download Center or Volume Licensing site
  3. 3. Review Microsoft's official upgrade documentation for Dynamics 365 on-premises
  4. 4. Apply the update using the Dynamics 365 Deployment Manager or appropriate installation tool
  5. 5. Verify the update was successful by checking the system version and testing core functionality
Caveat On-premises upgrades may require downtime; test in a staging environment before production deployment

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

Fix this in Dynamics 365 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-62206 — 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-62206 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