dbcve.org
Sql Server 2022Application · Microsoft

CVE-2025-47954

HIGH · 8.8 CVSS v3.1 Published 2025-08-12
Fix available
A fix is available. Upgrade to 16.0.1145.1 / 16.0.4210.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 neutralization of special elements in SQL commands allows an authenticated attacker to execute arbitrary SQL code. This can lead to privilege escalation, potentially granting administrative access to database resources or underlying system.

MitigationImplement parameterized queries (prepared statements) or stored procedures with proper input validation to neutralize SQL injection vectors. Review and audit all database query implementations for improper input handling.

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 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. Confirm SQL Server 2022 is installed
    Run SELECT @@VERSION in SQL Server Management Studio or via sqlcmd to display version information
    Affected if The output shows Microsoft SQL Server 2022 as the installed instance
  2. Extract the exact build version number
    Run SELECT SERVERPROPERTY('ProductVersion') to get the precise version number (for example: 16.0.1140.1)
    Affected if A version number is returned showing the installed build
  3. Compare version against first affected range
    Check if the version is >= 16.0.1000.6 AND < 16.0.1145.1
    Affected if Version falls within this range, indicating the instance is vulnerable
  4. Compare version against second affected range
    Check if the version is >= 16.0.4003.1 AND < 16.0.4210.1
    Affected if Version falls within this range, indicating the instance is vulnerable
  5. Identify authentication requirements
    Review whether database users with standard SQL authentication have access to the affected query paths
    Affected if Authenticated users can reach the vulnerable SQL code path

The environment is affected if SQL Server 2022 is running and the ProductVersion falls within 16.0.1000.6-16.0.1145.1 or 16.0.4003.1-16.0.4210.1, allowing an authenticated user to inject malicious SQL commands.

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 16.0.1145.1 / 16.0.4210.1 or later
Fixed in 16.0.1145.116.0.4210.1
Interim mitigation

Implement parameterized queries (prepared statements) or stored procedures with proper input validation to neutralize SQL injection vectors. Review and audit all database query implementations for improper input handling.

Recommended fix High confidence

SQL Server 2022 version 16.0.4210.1 or later

  1. 1. Identify the current SQL Server 2022 version by running: SELECT @@VERSION;
  2. 2. For versions >= 16.0.1000.6 and < 16.0.1145.1: Plan upgrade to version 16.0.1145.1 or later
  3. 3. For versions >= 16.0.4003.1 and < 16.0.4210.1: Plan upgrade to version 16.0.4210.1 or later
  4. 4. Review Microsoft documentation for SQL Server 2022 upgrade procedures: https://learn.microsoft.com/en-us/sql/database-engine/install-windows/upgrade-sql-server
  5. 5. Test the upgrade in a non-production environment first
  6. 6. Ensure backups of all databases are verified before production upgrade
  7. 7. Apply the upgrade during a scheduled maintenance window
  8. 8. After upgrade, verify the version using: SELECT @@VERSION; to confirm successful patching
Caveat Standard SQL Server upgrade considerations apply - review release notes for any behavioral changes and test applications thoroughly before production deployment

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

Fix this in Sql Server 2022 Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing16.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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