CVE-2026-47647
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 · uneditedImproper access control in Microsoft Dynamics 365 allows an authorized attacker to elevate privileges 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 · moderate confidenceImproper access control in Microsoft Dynamics 365 allows an authorized attacker to elevate privileges over a network. This is a privilege escalation vulnerability where an attacker with valid credentials can gain higher-level access than intended by the system's access controls.
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 dataall versionsCVSS 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
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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.
-
Confirm Dynamics 365 deployment typeIdentify whether your Dynamics 365 instance is cloud-based (D365 Online) or on-premises. For cloud, check the Power Platform Admin Center. For on-premises, check the installed version via SQL Server or Dynamics 365 Installation Wizard.Affected if Any deployment type is potentially affected since all versions are vulnerable.
-
Review user security rolesOpen Dynamics 365 as an administrator, navigate to Settings > Security > Security Roles. Document all custom or elevated roles that grant more than basic user privileges, particularly those with Create/Write/Delete permissions on the User or Security Role entities.Affected if Users have been assigned roles that grant permissions beyond what their job function requires.
-
Audit role-to-user assignmentsGenerate a report of all users and their assigned security roles using Advanced Find or the Dynamics 365 Admin Center. Look for users assigned multiple administrative or elevated roles.Affected if A single user holds more than one elevated security role or has roles that provide超出其工作职责所需的权限.
-
Examine audit logs for privilege changesAccess the Audit Log in Dynamics 365 (Settings > Audit). Search for events related to changes in security roles, user access, or permission modifications within the past 30 days.Affected if Audit logs show unauthorized or unexpected changes to security roles or user permission levels.
-
Check for suspicious user behavior patternsReview system logs for users accessing data or features outside their typical scope, or for bulk data exports or modifications that align with privilege escalation activity.Affected if User activity shows access patterns inconsistent with their assigned security roles.
Your environment is affected if you run any version of Microsoft Dynamics 365, as all versions are listed as vulnerable to this privilege escalation flaw.
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.
From vendor dataApply Microsoft's security patch for Dynamics 365 when available. In the interim, enforce least-privilege access controls, audit user role assignments, and monitor for anomalous privilege escalation activities.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-47647 — 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-2026-47647 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