CVE-2025-53728
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 · uneditedExposure 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 · moderate confidenceInformation disclosure vulnerability in Microsoft Dynamics 365 (on-premises) allows an unauthenticated attacker to access sensitive data over a network. The CVSS 6.5 indicates the attack can be launched remotely with low complexity and no privileges required, but does not affect the confidentiality scope beyond the vulnerable component.
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>= 9.1, < 9.1.39.04CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Dynamics 365 on-premises deploymentVerify that the environment is Microsoft Dynamics 365 (on-premises) and not Dynamics 365 Online/Cloud. Check deployment documentation or contact the system administrator to confirm the deployment type.Affected if The environment is running Microsoft Dynamics 365 on-premises.
-
Locate the installed Dynamics 365 versionRetrieve the installed version of Dynamics 365. For on-premises deployments, this is typically available through the Dynamics 365 Deployment Manager, the Microsoft Dynamics 365 Installation Wizard, or by querying the system where Dynamics 365 Server is installed.Affected if The installed version cannot be determined or the system is not Dynamics 365 on-premises.
-
Compare version against affected rangeCompare the installed version to the vulnerable range: version 9.1 or later but earlier than 9.1.39.04. Any version that starts with 9.1 and is below 9.1.39.04 is affected.Affected if The installed version is 9.1.x where x is less than 39.04 (for example, 9.1.20.0, 9.1.38.0 would be vulnerable, while 9.1.39.04 or later is not).
A system is affected if it runs Microsoft Dynamics 365 on-premises with version 9.1 or later but earlier than 9.1.39.04.
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 · scoped9.1.39.04
Apply Microsoft security updates for Dynamics 365 on-premises when available and review access control configurations to ensure proper authentication and authorization controls are enforced.
9.1.39.04 or later
- Backup your Microsoft Dynamics 365 (on-premises) database and configuration
- Download the Dynamics 365 version 9.1.39.04 or later update from the Microsoft Download Center or through your licensing portal
- Review the update installation prerequisites and documentation provided by Microsoft
- Apply the update to your Dynamics 365 on-premises environment following Microsoft's official installation guide
- After installation, verify the update was successful by checking the Dynamics 365 version in the system
- Confirm the vulnerability is remediated by reviewing the installed version is 9.1.39.04 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-53728 — 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-53728 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