dbcve.org
Sql Server 2016Application · Microsoft

CVE-2025-49719

HIGH · 7.5 CVSS v3.1 Published 2025-07-08
Fix available
A fix is available. Upgrade to 13.0.6460.7 / 13.0.7055.9 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable 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 input validation in SQL Server allows an unauthorized attacker to disclose information 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

Improper input validation in SQL Server enables an unauthenticated remote attacker to disclose sensitive information. The vulnerability stems from insufficient validation of user-supplied input, likely allowing injection of malicious queries or manipulation of database parameters.

MitigationImplement strict input validation on all user-facing database queries, use parameterized statements/prepared queries, and apply the latest Microsoft SQL Server security updates. Restrict network exposure of SQL Server instances.

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.6460.7>= 13.0.7000.253, < 13.0.7055.9
Sql Server 2017Application
Affected:>= 14.0.1000.169, < 14.0.2075.8>= 14.0.3006.16, < 14.0.3495.9
Sql Server 2019Application
Affected:>= 15.0.2000.5, < 15.0.2135.5>= 15.0.4003.23, < 15.0.4435.7
Sql Server 2022Application
Affected:>= 16.0.1000.6, < 16.0.1140.6>= 16.0.4003.1, < 16.0.4200.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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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' in SQL Server Management Studio or execute 'sqlcmd -S <server> -Q "SELECT @@VERSION"' from command line
    Affected if The version output matches any of the affected ranges: SQL Server 2016 (13.0.6300.2 to 13.0.6460.6 or 13.0.7000.253 to 13.0.7055.8), SQL Server 2017 (14.0.1000.169 to 14.0.2075.7 or 14.0.3006.16 to 14.0.3495.8), SQL Server 2019 (15.0.2000.5 to 15.0.2135.4 or 15.0.4003.23 to 15.0.4435.6), SQL Server
  2. Verify SQL Server is listening on network
    Check SQL Server Configuration Manager > SQL Server Network Configuration > Protocols for <InstanceName>, ensure TCP/IP is enabled. Alternatively run 'netstat -an | findstr 1433' (or instance-specific port) to see if port is listening
    Affected if TCP/IP protocol is enabled and the SQL Server port is bound to a network interface accessible to unauthenticated users
  3. Confirm authentication mode
    Run query: 'SELECT serverproperty('IsIntegratedSecurityOnly')'. Value 0 means Mixed Mode (SQL authentication enabled), Value 1 means Windows-only authentication
    Affected if IsIntegratedSecurityOnly returns 0, indicating SQL Server authentication is enabled allowing unauthenticated connections
  4. Check for user-facing query endpoints
    Review any application connection strings or web applications that connect to this SQL Server instance. Examine SQL Server error logs for recent query activity from unauthenticated sources using 'EXEC sp_readerrorlog'
    Affected if Applications connect to this SQL Server using SQL authentication or the instance accepts connections from unauthenticated network sources

Your SQL Server is vulnerable if it runs an affected version listed above AND is network-accessible with SQL authentication enabled, allowing unauthenticated attackers to send malicious input to database queries.

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.6460.7 / 13.0.7055.9 / 14.0.2075.8 or later
Fixed in 13.0.6460.713.0.7055.914.0.2075.8
Interim mitigation

Implement strict input validation on all user-facing database queries, use parameterized statements/prepared queries, and apply the latest Microsoft SQL Server security updates. Restrict network exposure of SQL Server instances.

Recommended fix High confidence

SQL Server 2016 SP3 CU19 (13.0.7055.9) or later; SQL Server 2017 CU31 (14.0.3495.9) or later; SQL Server 2019 CU25 (15.0.4435.7) or later; SQL Server 2022 CU10 (16.0.4200.1) or later

  1. 1. Identify your current SQL Server version by running: SELECT @@VERSION
  2. 2. For SQL Server 2016: Apply Cumulative Update 19 (13.0.7055.9) or later for Service Pack 3, or Cumulative Update 7 (13.0.6460.7) or later for Service Pack 2
  3. 3. For SQL Server 2017: Apply Cumulative Update 31 (14.0.3495.9) or later for GDR, or Cumulative Update 26 (14.0.2075.8) or later for the original release
  4. 4. For SQL Server 2019: Apply Cumulative Update 25 (15.0.4435.7) or later for GDR, or Cumulative Update 14 (15.0.2135.5) or later for the original release
  5. 5. For SQL Server 2022: Apply Cumulative Update 10 (16.0.4200.1) or later for GDR, or Cumulative Update 7 (16.0.1140.6) or later for the original release
  6. 6. Download the appropriate update from: https://learn.microsoft.com/en-us/sql/database-engine/install-windows/latest-updates-for-microsoft-sql-server
  7. 7. Before applying in production, test the update in a non-production environment to verify application compatibility
  8. 8. Ensure you have a verified backup before applying any updates
Caveat Standard SQL Server cumulative update - minimal risk but always test applications after updates; GDR updates contain only security fixes and are lower risk than cumulative updates

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-49719 — 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-49719 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