dbcve.org
Sql Server 2016Application · Microsoft

CVE-2025-53727

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 allows authenticated attackers to inject malicious SQL commands and elevate privileges to higher-level database roles or administrative accounts. The vulnerability stems from improper neutralization of special SQL elements in user-supplied input processed by the database.

MitigationRemediate by replacing vulnerable dynamic SQL queries with parameterized queries/stored procedures, implementing strict input validation, and applying the principle of least privilege to database accounts to limit impact of potential compromise.

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 the installed SQL Server version
    Run query: SELECT @@VERSION or check SQL Server Error Log for the version entry at startup
    Affected if The version falls within any of these vulnerable ranges: 2016 (13.0.6300.2-13.0.6465.1 or 13.0.7000.253-13.0.7060.1), 2017 (14.0.1000.169-14.0.2080.1 or 14.0.3006.16-14.0.3500.1), 2019 (15.0.2000.5-15.0.2140.1 or 15.0.4003.23-15.0.4440.1), 2022 (16.0.1000.6-16.0.1145.1 or 16.0.4003.1-16.0.4210.1)
  2. Identify dynamic SQL execution in application code
    Review application source code and stored procedures for use of EXEC(), EXEC sp_executesql with string concatenation, or openquery with dynamic strings
    Affected if Dynamic SQL is constructed using string concatenation rather than parameterized queries
  3. Audit database user privileges
    Run: SELECT member_name, role_name FROM sys.database_role_members rm JOIN sys.database_principals p ON rm.member_principal_id = p.principal_id JOIN sys.database_principals r ON rm.role_principal_id = r.principal_id
    Affected if Users are assigned overly broad roles such as sysadmin, db_owner, or have elevated permissions beyond what their function requires
  4. Review recent SQL injection attempt indicators
    Check SQL Server Audit logs, default trace, or Extended Events for patterns like: unexpected single quotes, UNION SELECT, comment sequences (--, /*), or sp_executesql calls with unusual parameter patterns
    Affected if Audit logs show suspicious SQL patterns indicative of injection attempts

You are affected if your SQL Server version is within any of the listed vulnerable ranges AND your environment uses dynamic SQL with user-controllable input that could be injected.

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

Remediate by replacing vulnerable dynamic SQL queries with parameterized queries/stored procedures, implementing strict input validation, and applying the principle of least privilege to database accounts to limit impact of potential compromise.

Recommended fix High confidence

Upgrade to the latest Cumulative Update for your SQL Server version branch (2016: 13.0.6465.1+ or 13.0.7060.1+, 2017: 14.0.2080.1+ or 14.0.3500.1+, 2019: 15.0.2140.1+ or 15.0.4440.1+, 2022: 16.0.1145.1+ or 16.0.4210.1+)

  1. 1. Identify the current SQL Server version by running: SELECT @@VERSION;
  2. 2. Determine the appropriate servicing branch for your version from the affected version ranges listed
  3. 3. Download the latest cumulative update (CU) for your SQL Server version from the Microsoft Update Catalog or Microsoft's SQL Server release notes
  4. 4. Apply the cumulative update during a scheduled maintenance window
  5. 5. For SQL Server 2016: upgrade to version 13.0.6465.1 (Servicing branch 13.0.6300.x) or 13.0.7060.1 (Servicing branch 13.0.7000.x)
  6. 6. For SQL Server 2017: upgrade to version 14.0.2080.1 (Servicing branch 14.0.1000.x) or 14.0.3500.1 (Servicing branch 14.0.3006.x)
  7. 7. For SQL Server 2019: upgrade to version 15.0.2140.1 (Servicing branch 15.0.2000.x) or 15.0.4440.1 (Servicing branch 15.0.4003.x)
  8. 8. For SQL Server 2022: upgrade to version 16.0.1145.1 (Servicing branch 16.0.1000.x) or 16.0.4210.1 (Servicing branch 16.0.4003.x)
Caveat Standard SQL Server cumulative update risks apply - test in non-production environment first as some updates may affect features or third-party integrations

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
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
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,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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