dbcve.org
Configuration Manager 2403Application · Microsoft

CVE-2025-59213

HIGH · 8.8 CVSS v3.1 Published 2025-10-14
Fix available
A fix is available. Upgrade to 5.00.9128.1035 / 5.00.9132.1029 or later.
See remediation →
93/100
Remediation priority · Urgent
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
Improper neutralization of special elements used in an sql command ('sql injection') in Microsoft Configuration Manager allows an unauthorized 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 confidence

SQL injection vulnerability in Microsoft Configuration Manager allows an unauthorized attacker to elevate privileges over an adjacent network. The vulnerability stems from improper neutralization of special elements in SQL commands, enabling authenticated or adjacent network attackers to manipulate SQL queries and potentially gain elevated database access.

MitigationApply Microsoft-provided security patches for Configuration Manager when available; ensure database accounts follow least privilege principles; review and harden database query pathways in the ConfigMgr environment.

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
Configuration Manager 2403Application
Affected:< 5.00.9128.1035
Configuration Manager 2409Application
Affected:< 5.00.9132.1029
Configuration Manager 2503Application
Affected:< 5.00.9135.1008

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

CVSS:3.1/AV:A/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed Microsoft Configuration Manager version
    Access the Configuration Manager administration console and navigate to the 'About Configuration Manager' option in the console tree (typically under the site node), or use the Get-CMApplication cmdlet or WMI to query the site version programmatically
    Affected if The detected version falls within the following vulnerable ranges: version 2403 builds earlier than 5.00.9128.1035, version 2409 builds earlier than 5.00.9132.1029, or version 2503 builds earlier than 5.00.9135.1008
  2. Confirm the branch and build number
    In the console, verify both the branch (such as 2403, 2409, or 2503) and the full build number displayed in the version details
    Affected if The build number is lower than the specific thresholds for your branch (5.00.9128.1035 for 2403, 5.00.9132.1029 for 2409, or 5.00.9135.1008 for 2503)
  3. Assess network accessibility to the SQL Server backend
    Review network segmentation and firewall rules to determine whether users or systems on the adjacent network can reach the SQL Server instance hosting the Configuration Manager database
    Affected if The SQL database is accessible from network segments accessible to untrusted or adjacent network attackers, which would enable them to exploit the SQL injection flaw if they obtain valid credentials

Your environment is affected if you are running any Microsoft Configuration Manager version 2403, 2409, or 2503 with a build number below the fixed thresholds (5.00.9128.1035, 5.00.9132.1029, or 5.00.9135.1008 respectively) and the SQL database is network-accessible from an adjacent network segment.

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 5.00.9128.1035 / 5.00.9132.1029 / 5.00.9135.1008 or later
Fixed in 5.00.9128.10355.00.9132.10295.00.9135.1008
Interim mitigation

Apply Microsoft-provided security patches for Configuration Manager when available; ensure database accounts follow least privilege principles; review and harden database query pathways in the ConfigMgr environment.

Recommended fix High confidence

Upgrade to the appropriate fixed version: 5.00.9128.1035 (branch 2403), 5.00.9132.1029 (branch 2409), or 5.00.9135.1008 (branch 2503)

  1. Identify your current Configuration Manager version by checking the console or site server
  2. Determine which branch (2403, 2409, or 2503) your deployment is running
  3. For Configuration Manager 2403: Upgrade to version 5.00.9128.1035 or later
  4. For Configuration Manager 2409: Upgrade to version 5.00.9132.1029 or later
  5. For Configuration Manager 2503: Upgrade to version 5.00.9135.1008 or later
  6. Apply the upgrade following Microsoft's standard Configuration Manager update procedures
  7. Verify the update was successful and the site is functioning normally
Caveat Standard Configuration Manager update best practices apply; ensure proper backups and testing in non-production first

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

Fix this in Configuration Manager 2403 Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing16.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,160.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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