dbcve.org
Windows Admin CenterApplication · Microsoft

CVE-2025-29819

MEDIUM · 6.2 CVSS v3.1 Published 2025-04-08
Fix available
A fix is available. Upgrade to 0.45.0.0 / 2410 or later.
See remediation →
67/100
Remediation priority · Elevated
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
External control of file name or path in Azure Portal Windows Admin Center allows an unauthorized 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 · high confidence

This is a path traversal vulnerability in Azure Portal's Windows Admin Center where an attacker can control file paths to read local files on the system, leading to unauthorized information disclosure.

MitigationApply Microsoft's security patches for Azure Portal Windows Admin Center. Verify that all Azure Portal deployments have the latest security updates installed.

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
Windows Admin CenterApplication
Affected:< 0.45.0.0< 2410

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

CVSS:3.1/AV:L/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. Identify Windows Admin Center installation
    Check for Windows Admin Center installation by looking for the service in Services.msc, or check for the installation directory (typically C:\Program Files\Windows Admin Center), or look for the Web Platform Installer entry
    Affected if Windows Admin Center is installed and accessible via Azure Portal
  2. Determine installed Windows Admin Center version
    Open Windows Admin Center and navigate to the About page, or check the installed version from Programs and Features, or run 'Get-WmiObject -Class Win32_Product' to query the installed version
    Affected if The installed version is below 0.45.0.0 or below build 2410
  3. Check if Azure Portal integration is enabled
    Inspect Windows Admin Center settings or check for Azure Portal connector configuration files in the installation directory, typically found in the config or connections subfolder
    Affected if Windows Admin Center is connected to or accessible through Azure Portal
  4. Verify web service configuration
    Review the Windows Admin Center web service configuration files (usually in the installation folder under config\settings.json or similar) for any exposed endpoints that handle file operations
    Affected if File handling endpoints are exposed without proper path validation

You are affected if Windows Admin Center is installed and accessible via Azure Portal, and the installed version is below 0.45.0.0 or build 2410, as this allows path traversal attacks to read local files.

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 0.45.0.0 / 2410 or later
Fixed in 0.45.0.02410
Interim mitigation

Apply Microsoft's security patches for Azure Portal Windows Admin Center. Verify that all Azure Portal deployments have the latest security updates installed.

Recommended fix High confidence

Windows Admin Center 0.45.0.0 or version 2410 and later

  1. Download Windows Admin Center version 0.45.0.0 (or version 2410 and later) from the official Microsoft Download Center
  2. Back up your current Windows Admin Center configuration and settings
  3. Install the Windows Admin Center update using the MSI installer or your preferred deployment method
  4. Follow Microsoft's upgrade documentation to complete the installation
  5. Verify the installation completed successfully and the service is running
  6. Confirm the path traversal vulnerability is resolved by testing file access controls

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

Fix this in Windows Admin Center Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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