Microsoft Configuration Manager SQL Injection Vulnerability
CVE-2024-43468 is a security vulnerability in Microsoft Configuration Manager, added to CISA KEV on February 12, 2026. Patch order: second of four.
What is CVE-2024-43468?
Microsoft Configuration Manager contains an SQL injection vulnerability. An unauthenticated attacker could exploit this vulnerability by sending specially crafted requests to the target environment which are processed in an unsafe manner enabling the attacker to execute commands on the server and/or underlying database.
Who is affected by CVE-2024-43468?
Affects anyone running Microsoft Configuration Manager. Microsoft products in a small practice typically sit close to credentials, email, or document workflows — treat the patch as in-scope.
What should I do about CVE-2024-43468?
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
The action above is CISA's wording. The directive it names, BOD 22-01, was revoked by BOD 26-04 on June 10, 2026; CISA's catalog still carries the older text for this entry.
If you don't have someone in-house to verify the patch deployed across every endpoint — or you're not sure whether you're affected — that's exactly the kind of triage we do. Request a free review.
Insurance readiness
Your insurer will ask if this is patched.
Unpatched entries on CISA's Known Exploited Vulnerabilities list are exactly what cyber-insurance carrier questionnaires probe for, and knowing which controls they check is how you keep a renewal from stalling.
Get the free carrier questionnaire →Severity
CVSS base score: 9.8 — CRITICAL
Weakness classification: CWE-89
Microsoft fix
- KB29166583 (Security Update)
Microsoft Exploitability Index (assessed at update release): Exploitation Less Likely
This CVE is on CISA's Known Exploited Vulnerabilities catalog. Microsoft's index reflects their release-time forecast, not current observed activity, and is not automatically revised upward when exploitation appears later.
Vendor workaround
No vendor workaround published. Patching is the only fix.
CISA due date
CISA's listed due date: March 5, 2026.
Federal civilian agencies work under CISA's Binding Operational Directive 26-04, which replaced BOD 22-01 on June 10, 2026. It sets the deadline for each affected system by:
- How exposed that system is to the internet
- Whether the attack can be automated
- How much control it gives an attacker
Its table gives catalogued vulnerabilities 3 or 14 days.
None of this binds a private business, but treat the date as a strong recommendation, especially if you handle regulated data (HIPAA, GLBA, ABA model rules).
EPSS
EPSS score: 81.0% — higher than 100% of all scored CVEs.
EPSS estimates the probability of exploitation activity in the next 30 days. Every entry on this site is already confirmed exploited, so read it as relative urgency among the things you still have open, not as permission to wait.
Source
This entry comes from CISA's Known Exploited Vulnerabilities catalog, public US-Government data we pull daily. The plain-language framing and the what-to-do guidance above are ours. View the original entry on cisa.gov.