Skip to main content
CVE-2025-53727VulnerabilityPublished Updated

CVE-2025-53727: Microsoft SQL Server 2016 Service Pack 3 (GDR) · SQL Injection

Affects Microsoft SQL Server 2016 Service Pack 3 (GDR)Source CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.1% chance of exploitation in 30 days – higher than 66% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Aug 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
Microsoft Microsoft SQL Server 2016 Service Pack 3 (GDR)Affected
  • =13.0.0
Fixed in–

AI-suggested

1. Apply patches or updates from Microsoft as soon as they become available for SQL Server 2016 Service Pack 3 (GDR). 2. Until patches are released, restrict network access to SQL Server instances using firewalls and network segmentation, limiting connections to trusted hosts only. 3. Implement strict input validation and parameterized queries in all applications interacting with the SQL Server to prevent injection of malicious SQL commands. 4. Employ least privilege principles, ensuring users and applications have only the minimum necessary permissions on the database. 5. Monitor SQL Server logs and network traffic for unusual or unauthorized query patterns indicative of injection attempts. 6. Conduct regular security assessments and penetration testing focused on database security. 7. Educate developers and database administrators on secure coding and configuration practices to reduce injection risks. 8. Consider deploying Web Application Firewalls (WAFs) or database activity monitoring tools that can detect and block SQL injection attempts in real time.

Description

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.

References

Community reviews

Loading reviews…