CVE-2025-47179
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 Configuration Manager allows an authorized attacker to elevate privileges 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 confidenceThis is a local privilege escalation vulnerability in Microsoft Configuration Manager caused by improper access control. An attacker who already has authorized access to the system can exploit insufficient authorization checks to elevate their privileges to a higher level within the local system.
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< 5.00.9128.1037< 5.00.9132.1031< 5.0.9135.1013CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/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.
-
Identify the installed Microsoft Configuration Manager versionOpen the Configuration Manager console, navigate to Administration > Site Configuration > Sites, and view the Site Component Information or use PowerShell: Get-CMApplication -ErrorAction SilentlyContinue; alternatively check the registry at HKLM\SOFTWARE\Microsoft\SMS\Identification for the version valueAffected if Version cannot be determined or retrieved from the system
-
Determine the Configuration Manager release branchCheck if the version corresponds to the 2403, 2409, or 2503 release branch by examining the major version number in the format 5.00.xxxx.xxxxAffected if The installed version does not belong to branches 2403, 2409, or 2503
-
Compare against vulnerable version rangesReview the installed version number and compare it to the following vulnerable thresholds: 2403 branch versions below 5.00.9128.1037, 2409 branch versions below 5.00.9132.1031, 2503 branch versions below 5.0.9135.1013Affected if The installed version falls below any of these three threshold values for its respective branch, indicating the missing authorization fix
-
Verify the security update is not appliedCheck Windows Update history or the Microsoft Update Catalog for installation records of a security update addressing CVE-2025-47179 applied to the Configuration Manager site server(s)Affected if No corresponding security update for CVE-2025-47179 appears in the update history and the version remains in the vulnerable range
The environment is affected if the installed Microsoft Configuration Manager version belongs to branch 2403, 2409, or 2503 and falls below the respective fixed version thresholds, and no corresponding security update has been applied.
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 · scoped5.00.9128.10375.00.9132.10315.0.9135.1013
Apply the Microsoft security update for CVE-2025-47179 once released through Windows Update or the Microsoft Update Catalog. Verify that the Configuration Manager hierarchy is fully patched and monitor for any unusual privilege escalation attempts.
Configuration Manager 2503 branch to version 5.0.9135.1013 or later (or respective fixed version for 2403/2409 branches)
- Identify the current Microsoft Configuration Manager version from the administration console or site hierarchy settings
- Determine which branch (2403, 2409, or 2503) is currently deployed
- Obtain the cumulative update package for the target fixed version from Microsoft Update Catalog or the Microsoft licensing portal
- Create a backup of the Configuration Manager database and site server state before applying updates
- Run the setup.exe from the extracted update package on the primary site server
- Follow the Configuration Manager update installation wizard, accepting license terms
- Monitor the update progress in the Configuration Manager console under Administration > Updates and Servicing
- Verify the site version matches the target fixed version (5.00.9128.1037 or higher for 2403, 5.00.9132.1031 or higher for 2409, 5.0.9135.1013 or higher for 2503) after installation completes
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47179 — 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-47179 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