Sql Server 2016Application · Microsoft

CVE-2025-49759

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

NVD · unedited

Improper neutralization of special elements used in an sql command ('sql injection') in SQL Server allows an authorized attacker to elevate privileges over a network.

Technical summary

dbcve analysis · moderate confidence

This is an SQL injection vulnerability in Microsoft SQL Server where improper neutralization of special elements in SQL commands allows an authenticated attacker to execute arbitrary SQL statements and elevate privileges to higher-level database roles.

MitigationRemediate by refactoring vulnerable code to use parameterized queries or prepared statements instead of string concatenation, apply the principle of least privilege to database user accounts, and perform input validation on all user-supplied data before incorporating it into SQL commands.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

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

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?

dbcve checks

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

Identify SQL Server version

Execute SELECT @@VERSION in SQL Server Management Studio or via sqlcmd: sqlcmd -S servername -E -Q "SELECT @@VERSION"

Affected if The version output does not match any of the safe version ranges (13.0.6465.1-13.0.7060.1, 13.0.7060.1+, 14.0.2080.1-14.0.3500.1, 14.0.3500.1+, 15.0.2140.1-15.0.4440.1, 15.0.4440.1+, 16.0.1145.1-16.0.4210.1, 16.0.4210.1+)
Verify exact build number

Query SELECT SERVERPROPERTY('ProductVersion'), SERVERPROPERTY('ProductLevel'), SERVERPROPERTY('Edition')

Affected if ProductVersion falls within any of these ranges: 13.0.6300.2-13.0.6465.1, 13.0.7000.253-13.0.7060.1, 14.0.1000.169-14.0.2080.1, 14.0.3006.16-14.0.3500.1, 15.0.2000.5-15.0.2140.1, 15.0.4003.23-15.0.4440.1, 16.0.1000.6-16.0.1145.1, 16.0.4003.1-16.0.4210.1
Confirm application uses dynamic SQL

Review application source code for SQL query construction patterns using string concatenation (e.g., "SELECT * FROM users WHERE id = '" + userInput + "'") rather than parameterized queries or stored procedures

Affected if Application code constructs SQL commands through string concatenation with unvalidated user input
Check database user privileges

Query SELECT * FROM sys.database_principals for user roles, and review application database login mappings

Affected if Application database account has elevated privileges beyond what the application functionality requires (e.g., db_owner, db_securityadmin, or unnecessary server-level roles)

You are affected if your SQL Server version falls within any of the listed affected ranges AND your application uses string-concatenated SQL queries with database user accounts that have elevated privileges.

Generated from the published advisory. Verify against your own configuration.

Remediation

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

Remediate by refactoring vulnerable code to use parameterized queries or prepared statements instead of string concatenation, apply the principle of least privilege to database user accounts, and perform input validation on all user-supplied data before incorporating it into SQL commands.

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

Identify the currently installed SQL Server version by running 'SELECT @@VERSION' in SQL Server Management Studio
Determine which version branch your current build belongs to (2016, 2017, 2019, or 2022)
For SQL Server 2016: Upgrade to version 13.0.6465.1 (Service Pack 3 with latest cumulative update) or version 13.0.7060.1 (latest available for that branch)
For SQL Server 2017: Upgrade to version 14.0.2080.1 (Cumulative Update 31) or version 14.0.3500.1 (latest available for that branch)
For SQL Server 2019: Upgrade to version 15.0.2140.1 (Cumulative Update 24) or version 15.0.4440.1 (latest available for that branch)
For SQL Server 2022: Upgrade to version 16.0.1145.1 (Cumulative Update 11) or version 16.0.4210.1 (latest available for that branch)
Download the appropriate update from Microsoft Update Catalog or use Windows Update
Apply the update in a test environment first, then schedule production deployment during maintenance window

Caveat Standard SQL Server update - minimal breaking changes expected; always test in non-production first

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

Fix this in Sql Server 2016 Scoped from the published advisory

Consultation6.0 h
Implementation12.0 h
Testing6.0 h
Review / QA3.0 h

27.0 hours of engineering $4,800

Get the upgrade done

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

msrc.microsoft.comVendor Advisory
nvd.nist.govNVD record

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-49759 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2025-49759?

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.

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

At a glance

A fix existsUpgrade to 13.0.6465.1 / 13.0.7060.1 or later

Severity 8.8 High

Exploit likelihood EPSS, next 30 days 1.1%

Affects: Sql Server 2016

Remediation

A high-priority fix

Fix this in Sql Server 2016 27 hrs · Moderate

Typical engagement from $4,800

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2025-49759 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References