dbcve.org
Dynamics 365 Business Central 2023Application · Microsoft

CVE-2025-29821

MEDIUM · 5.5 CVSS v3.1 Published 2025-04-08
Fix available
A fix is available. Upgrade to 23.18.32409 / 24.12.32447 or later.
See remediation →
57/100
Remediation priority · Elevated
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
Improper input validation in Dynamics Business Central allows an authorized attacker to disclose information locally.

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 confidence

Improper input validation in Microsoft Dynamics Business Central allows an authorized attacker to disclose information locally. The vulnerability stems from insufficient validation of user inputs, which could enable a local attacker with valid credentials to access sensitive information they should not have access to.

MitigationApply the vendor patch when released through Microsoft Update. In the meantime, restrict local access to trusted personnel and monitor for unusual local access patterns.

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 365 Business Central 2023Application
Affected:>= 23.1.13812, < 23.18.32409
Dynamics 365 Business Central 2024Application
Affected:< 24.12.32447>= 25.1.25900, < 25.6.32556
Dynamics 365 Business Central 2025Application
Affected:< 26.0.32481

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/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. Identify installed Business Central version via PowerShell
    Open PowerShell as administrator and run: Get-NAVServerInstance -ErrorAction SilentlyContinue | Select-Object ServerInstance, Version, State. Alternatively, check the Windows Services list for 'Microsoft Dynamics 365 Business Central Server' service and view its properties to find the version.
    Affected if The displayed version falls within any of the affected ranges: 23.1.13812 to 23.18.32409 (2023), 24.x to 24.12.32447 or 25.1.25900 to 25.6.32556 (2024), or below 26.0.32481 (2025).
  2. Confirm the Business Central year/season release
    The version number structure indicates the release year: versions starting with 23.x are 2023, 24.x are 2024, 25.x are early 2024 service update, and 26.x is 2025. Verify which release channel your instance belongs to by checking the version number prefix.
    Affected if Your instance is any 2023, 2024, or 2025 release that matches the version ranges in step 1.
  3. Check if local authentication is enabled
    This vulnerability requires a local attacker with valid credentials. Verify local Windows authentication methods are in use by reviewing the Business Central Server configuration in the Dynamics 365 Administration Center or via PowerShell: Get-NavServerUser -ServerInstance <instance> | Where-Object {$_.AuthenticationEmail -eq $null}.
    Affected if Local Windows authentication or database authentication is configured, allowing local users to log in with valid credentials.

You are affected if your Business Central installation version matches any of the affected version ranges for 2023, 2024, or 2025 releases AND local user authentication is enabled.

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 23.18.32409 / 24.12.32447 / 25.6.32556 or later
Fixed in 23.18.3240924.12.3244725.6.32556
Interim mitigation

Apply the vendor patch when released through Microsoft Update. In the meantime, restrict local access to trusted personnel and monitor for unusual local access patterns.

Recommended fix High confidence

Dynamics 365 Business Central 2023 (23.18+), 2024 (24.12+ or 25.6+), or 2025 (26.0+) depending on current release wave

  1. 1. Identify the current Dynamics 365 Business Central version by navigating to the Business Central admin center or checking the system information in the client.
  2. 2. Determine which release wave (2023, 2024, or 2025) the current installation belongs to based on the version number.
  3. 3. For Business Central 2023: Upgrade to version 23.18.32409 or later.
  4. 4. For Business Central 2024: If on version 24.x, upgrade to 24.12.32447 or later. If on version 25.x, upgrade to 25.6.32556 or later.
  5. 5. For Business Central 2025: Upgrade to version 26.0.32481 or later.
  6. 6. Schedule the upgrade during a maintenance window to minimize business impact.
  7. 7. After upgrading, verify the system is operational and test critical business workflows.
  8. 8. Review release notes for the target version to ensure all dependencies and integrations remain compatible.
Caveat Check release notes for potential breaking changes; major version upgrades may require testing of extensions and customizations

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

Fix this in Dynamics 365 Business Central 2023 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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