dbcve.org
Sql Server 2016Application · Microsoft

CVE-2025-49758

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 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 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 SQL Server where improper input handling allows an authorized attacker to inject malicious SQL commands, potentially elevating privileges from their current authorized access level to higher privileges.

MitigationImplement parameterized queries or stored procedures with proper input validation, apply least privilege principles to database accounts, and ensure web-facing applications use parameterized interfaces rather than dynamic SQL construction.

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. Determine SQL Server version
    Run query: SELECT @@VERSION; or via PowerShell: Get-ItemProperty 'HK:\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL16.INSTANCE_NAME\Setup' | Select-Object PatchLevel
    Affected if Version number falls within any of the affected ranges: 2016 (13.0.6300.2 to 13.0.6465.1 or 13.0.7000.253 to 13.0.7060.1), 2017 (14.0.1000.169 to 14.0.2080.1 or 14.0.3006.16 to 14.0.3500.1), 2019 (15.0.2000.5 to 15.0.2140.1 or 15.0.4003.23 to 15.0.4440.1), 2022 (16.0.1000.6 to 16.0.1145.1 or 16.0.40

If the installed SQL Server version falls within the affected ranges AND the application uses dynamic SQL queries constructed from user input, the environment is vulnerable to this SQL injection flaw.

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

Implement parameterized queries or stored procedures with proper input validation, apply least privilege principles to database accounts, and ensure web-facing applications use parameterized interfaces rather than dynamic SQL construction.

Recommended fix High confidence

SQL Server 2016: upgrade to 13.0.6465.1 or later (or 13.0.7060.1+); SQL Server 2017: upgrade to 14.0.2080.1 or later (or 14.0.3500.1+); SQL Server 2019: upgrade to 15.0.2140.1 or later (or 15.0.4440.1+); SQL Server 2022: upgrade to 16.0.1145.1 or later (or 16.0.4210.1+)

  1. Identify the current SQL Server version by running 'SELECT @@VERSION'
  2. Plan a maintenance window for the upgrade process
  3. Perform a full backup of all user databases and system databases
  4. Upgrade SQL Server to the appropriate fixed version: SQL Server 2016 to 13.0.6465.1 or later (or 13.0.7060.1+), SQL Server 2017 to 14.0.2080.1 or later (or 14.0.3500.1+), SQL Server 2019 to 15.0.2140.1 or later (or 15.0.4440.1+), SQL Server 2022 to 16.0.1145.1 or later (or 16.0.4210.1+)
  5. After upgrade, verify the version with 'SELECT @@VERSION'
  6. Test critical applications and workloads to ensure functionality
  7. Monitor error logs for any post-upgrade issues
Caveat Standard SQL Server upgrade considerations apply - review compatibility settings and test applications before production deployment

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 / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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