CVE-2025-47178
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 neutralization of special elements used in an sql command ('sql injection') in Microsoft Configuration Manager allows an authorized attacker to execute code over an adjacent 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 confidenceSQL injection vulnerability in Microsoft Configuration Manager allows an authenticated attacker to inject malicious SQL commands, potentially leading to code execution. The attack occurs over an adjacent network, meaning the attacker must have network access to the same network segment as the target 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.9135.1003CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:L/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.
-
Determine installed Configuration Manager versionOpen the Configuration Manager console, go to the About Microsoft Endpoint Configuration Manager option in the top left corner, or run PowerShell cmdlet Get-CMApplication with version display, or check the registry key HKLM\SOFTWARE\Microsoft\SMS\Setup for the Version valueAffected if The installed version is Microsoft Configuration Manager 2503 and the version number is less than 5.00.9135.1003
-
Confirm the branch version is 2503In the console About screen, verify the build number matches the 2503 branch (current branch releases display as year-month format, e.g., 2503 means March 2025 release)Affected if The build shows 2503 as the branch release
-
Verify SQL Server service exposureCheck if the SQL Server instance used by Configuration Manager (typically the site database) is listening on network interfaces accessible from adjacent network segments. Use netstat -an or SQL Server Configuration Manager to review listening addresses and ports (default 1433)Affected if SQL Server is bound to 0.0.0.0 or accessible from non-localhost interfaces on the adjacent network
-
Confirm authentication is enabledVerify that SQL Server authentication or Windows authentication is enabled and that there are user accounts with permissions to access the Configuration Manager database. Check SQL Server security configuration via SQL Server Management Studio or registryAffected if SQL authentication is enabled or domain/user accounts can authenticate to the SQL instance used by Configuration Manager
-
Check for public network bindingReview Windows Firewall rules and network adapter bindings to determine if Configuration Manager SQL ports (1433 default) or the SMS Executive service ports are exposed to public or untrusted network adaptersAffected if The site server has network adapters connected to less-trusted network segments where unauthenticated attackers could potentially reach SQL services
You are affected if running Configuration Manager version 2503 with build less than 5.00.9135.1003 AND the SQL database is accessible from adjacent network segments with valid authentication credentials available.
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.9135.1003
Apply vendor-provided patches for Microsoft Configuration Manager. Implement parameterized queries or prepared statements for all database operations. Review and restrict database permissions following least-privilege principles.
Configuration Manager version 5.00.9135.1003 (or later)
- Confirm current Configuration Manager version by navigating to the console About section
- Plan and schedule a maintenance window for the upgrade
- Review the Microsoft documentation for Configuration Manager current branch updates
- Download and apply Configuration Manager version 5.00.9135.1003 or later
- Verify the upgrade was successful by checking the console version
- Review site health and functionality post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47178 — 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-47178 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