CVE-2026-47301 in Microsoft Configuration Manager
Improper access control in Microsoft Configuration Manager allows an authorized attacker to elevate privileges over a network.
Quick answer
Microsoft Configuration Manager should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- Configuration Manager 2503
- Configuration Manager 2509
- Configuration Manager 2603
Fixed versions
- Apply the Microsoft security update for CVE-2026-47301
How to fix it
CVE-2026-47301 is a privilege escalation issue in Microsoft Configuration Manager. Update from Configuration Manager 2503 to Apply the Microsoft security update for CVE-2026-47301 or newer. Keep it simple: upgrade first, then test the normal user flow.
- Find every place where Microsoft Configuration Manager is installed or used.
- Upgrade Microsoft Configuration Manager to Apply the Microsoft security update for CVE-2026-47301 or a newer fixed release from the vendor.
- If you cannot upgrade right away, limit access to the affected feature until the update is done.
- Restart or redeploy the service if the product needs it after the update.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm the installed version is Apply the Microsoft security update for CVE-2026-47301 or newer.
- Run a normal login, admin, and user flow to make sure the site still works.
- Check logs for new errors after the update.
Related categories
Trusted references
FAQ
What is affected by CVE-2026-47301?
Microsoft Configuration Manager versions listed as affected should be reviewed: Configuration Manager 2503, Configuration Manager 2509, Configuration Manager 2603.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.