CVE-2025-55320
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 elevate privileges 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 with adjacent network access to inject malicious SQL commands, potentially elevating privileges by manipulating database queries that the application executes without proper input sanitization.
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.1035< 5.00.9132.1029< 5.00.9135.1008CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/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 installed Configuration Manager versionUse the SCCM console (Administration > Site Configuration > Sites) or run 'Get-CMApplication' PowerShell cmdlet to retrieve the site version, or check the registry key HKLM\SOFTWARE\Microsoft\SMS\Setup\Version on the site serverAffected if The version is 2403 with build lower than 5.00.9128.1035, or 2409 with build lower than 5.00.9132.1029, or 2503 with build lower than 5.00.9135.1008
-
Verify network accessibility of SCCM SQL Server endpointsCheck firewall rules and network segmentation around the SQL Server instance used by Configuration Manager. Identify if ports 1433 (TCP) or any custom SQL listening ports are exposed to untrusted adjacent network segmentsAffected if SQL Server ports used by SCCM are accessible from untrusted network segments beyond trusted administrative systems
-
Confirm account context used by SCCM database connectionsReview the SQL Server login and database user mappings associated with the SCCM site database. Check the security logs and SQL Server error logs for any evidence of unexpected or high-privilege account usage in the SCCM database contextAffected if The SCCM application uses SQL authentication with elevated privileges or the account has more database permissions than required for standard SCCM operations
-
Assess exposure to authenticated attackersEvaluate whether adjacent network users or systems could obtain valid credentials for SCCM administrative accounts. Review the account lockout policies and authentication requirements for accessing SCCM management points and distribution pointsAffected if Adjacent network access permits unauthorized or low-privilege users to authenticate to SCCM components without multi-factor authentication or strict access controls
A user is affected if their installed Configuration Manager version matches one of the vulnerable builds listed AND the SQL Server port is exposed to adjacent networks AND an authenticated attacker could leverage that access to inject SQL commands.
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.10355.00.9132.10295.00.9135.1008
Apply Microsoft Security Updates for Configuration Manager immediately. As an immediate control, restrict network access to the affected SCCM components to trusted administrative systems only, and audit database permissions for the account context used by SCCM SQL queries.
Configuration Manager 2403: 5.00.9128.1035 | Configuration Manager 2409: 5.00.9132.1029 | Configuration Manager 2503: 5.00.9135.1008
- Identify the current Configuration Manager version by navigating to the Administration workspace and selecting Site Configuration > Sites
- Determine which branch (2403, 2409, or 2503) is currently deployed
- Download the corresponding cumulative update from the Microsoft Update Catalog or Microsoft Download Center that contains the fixed version (5.00.9128.1035 for 2403, 5.00.9132.1029 for 2409, or 5.00.9135.1008 for 2503)
- Run the update package on the central administration site or primary site server
- Verify the update applied successfully by checking the version in the console matches the fixed version
- Monitor the site server and component status logs for any errors following the update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-55320 — 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-55320 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