dbcve.org
Sql Server 2016Application · Microsoft

CVE-2025-24999

HIGH · 8.8 CVSS v3.1 Published 2025-08-12
Fix available
A fix is available. Upgrade to 13.0.6465.1 / 13.0.7060.1 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 access control in SQL Server allows an authorized attacker to elevate privileges over a 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

This is an improper access control vulnerability in Microsoft SQL Server that allows an authenticated attacker to elevate their privileges beyond what should be permitted, potentially gaining administrative or sysadmin-level access. The attack can be carried out over the network, indicating the vulnerability is exploitable remotely by someone with valid database credentials.

MitigationApply the appropriate Microsoft SQL Server security update or patch for CVE-2025-24999. Review and audit SQL Server user role assignments and permissions following the patch to ensure no unauthorized privilege escalation occurred.

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
Sql Server 2016Application
Affected:>= 13.0.6300.2, < 13.0.6465.1>= 13.0.7000.253, < 13.0.7060.1
Sql Server 2017Application
Affected:>= 14.0.1000.169, < 14.0.2080.1>= 14.0.3006.16, < 14.0.3500.1
Sql Server 2019Application
Affected:>= 15.0.2000.5, < 15.0.2140.1>= 15.0.4003.23, < 15.0.4440.1
Sql Server 2022Application
Affected:>= 16.0.1000.6, < 16.0.1145.1>= 16.0.4003.1, < 16.0.4210.1

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

CVSS:3.1/AV:N/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 checks

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

  1. Retrieve SQL Server version
    Execute SELECT @@VERSION; in SQL Server Management Studio or via sqlcmd. Note the build number (e.g., 16.0.1000.6).
    Affected if The build number falls within any of the affected ranges: SQL Server 2016 (13.0.6300.2 to 13.0.6465.1 or 13.0.7000.253 to 13.0.7060.1), SQL Server 2017 (14.0.1000.169 to 14.0.2080.1 or 14.0.3006.16 to 14.0.3500.1), SQL Server 2019 (15.0.2000.5 to 15.0.2140.1 or 15.0.4003.23 to 15.0.4440.1), SQL Serv
  2. Confirm SQL Server edition and major version
    Execute SELECT SERVERPROPERTY('ProductVersion'), SERVERPROPERTY('ProductLevel'), SERVERPROPERTY('Edition'); to verify the exact edition and patch level.
    Affected if ProductLevel is not 'SP3' for SQL Server 2017 or 'RTM' with a build higher than the safe versions listed above.
  3. Identify network-exposed SQL Server instances
    Check if TCP/IP or named pipes are enabled in SQL Server Configuration Manager under SQL Server Network Configuration, and review firewall rules allowing inbound connections to port 1433 (default).
    Affected if SQL Server is listening on network interfaces and accessible from untrusted networks.
  4. Audit privileged role memberships
    Execute SELECT name, type_desc, is_disabled FROM sys.server_principals WHERE type IN ('S', 'U', 'G') AND is_disabled = 0; to list all enabled logins. Then run SELECT l.name AS login_name, r.name AS role_name FROM sys.server_role_members rm JOIN sys.server_principals r ON rm.role_principal_id = r.principal_id JOIN sys.server_principals l ON rm.member_principal_id = l.principal_id; to identify members of the sysadmin server role.
    Affected if Unexpected or unauthorized accounts have sysadmin role membership, indicating possible exploitation.

If the installed SQL Server build number falls within any of the affected version ranges AND the instance is network-accessible with valid authentication, the environment is likely affected by this privilege escalation vulnerability.

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 13.0.6465.1 / 13.0.7060.1 / 14.0.2080.1 or later
Fixed in 13.0.6465.113.0.7060.114.0.2080.1
Interim mitigation

Apply the appropriate Microsoft SQL Server security update or patch for CVE-2025-24999. Review and audit SQL Server user role assignments and permissions following the patch to ensure no unauthorized privilege escalation occurred.

Recommended fix High confidence

SQL Server 2016: 13.0.6465.1 or 13.0.7060.1 | SQL Server 2017: 14.0.2080.1 or 14.0.3500.1 | SQL Server 2019: 15.0.2140.1 or 15.0.4440.1 | SQL Server 2022: 16.0.1145.1 or 16.0.4210.1

  1. 1. Identify the exact version of SQL Server currently installed by running 'SELECT @@VERSION' in SQL Server Management Studio
  2. 2. Determine which version branch (RTM or Service Pack/Cumulative Update branch) your current installation belongs to
  3. 3. For SQL Server 2016: Upgrade to version 13.0.6465.1 (SP3 + CU4) or version 13.0.7060.1 (SP3 + later CU) depending on your branch
  4. 4. For SQL Server 2017: Upgrade to version 14.0.2080.1 (CU31) or version 14.0.3500.1 (later CU) depending on your branch
  5. 5. For SQL Server 2019: Upgrade to version 15.0.2140.1 (CU24) or version 15.0.4440.1 (later CU) depending on your branch
  6. 6. For SQL Server 2022: Upgrade to version 16.0.1145.1 (CU14) or version 16.0.4210.1 (later CU) depending on your branch
  7. 7. Download the appropriate update from Microsoft Update Catalog or use Windows Update
  8. 8. Apply the update during a maintenance window, ensuring backups are current
Caveat Standard SQL Server upgrade considerations apply - test in non-production environment first, ensure compatibility with existing applications and stored procedures

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

Fix this in Sql Server 2016 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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