Vulnerability record · CVE-2002-0721 · published 5 September 2002
CVE-2002-0721: Microsoft SQL Server weak permissions on extended stored procedures
Microsoft · Data Engine
Microsoft SQL Server 7.0 and 2000 installs extended stored procedures tied to helper functions with weak permissions. Unprivileged users, and possibly remote attackers, can execute xp_execresultset, xp_printstatements, or xp_displayparamstmt with administrator privileges. This is a privilege escalation flaw in default installations of an affected database server.
Description
Microsoft SQL Server 7.0 and 2000 installs with weak permissions for extended stored procedures that are associated with helper functions, which could allow unprivileged users, and possibly remote attackers, to run stored procedures with administrator privileges via (1) xp_execresultset, (2) xp_printstatements, or (3) xp_displayparamstmt.
AV:N/AC:L/Au:N/C:C/I:C/A:C
Automated analysis
high priorityThe flaw allows privilege escalation to administrator on a database server and has a very high EPSS score, though it is not in KEV and the record lacks modern exploit detail.
What it is
Microsoft SQL Server 7.0 and 2000 installs extended stored procedures tied to helper functions with weak permissions. Unprivileged users, and possibly remote attackers, can execute xp_execresultset, xp_printstatements, or xp_displayparamstmt with administrator privileges. This is a privilege escalation flaw in default installations of an affected database server.
Impact
An attacker gains the ability to run stored procedures with administrator privileges on the SQL Server instance, effectively escalating from an unprivileged database user to full control of the database service.
Attack surface
The flaw is reachable through the SQL Server interface, and the description states unprivileged users and possibly remote attackers can trigger it, so no special privileges are required; the record does not specify whether network exposure or authentication is mandatory beyond that.
Exploitation
Not listed in CISA KEV and no ransomware usage documented, but EPSS is 0.46307 (98.76th percentile), indicating a high modeled likelihood of exploitation; reference tags are limited to US Government Resource with no exploit tags.
What to do
- Apply the Microsoft security bulletin MS02-043 fix for SQL Server 7.0 and 2000.
- Restrict and audit permissions on the extended stored procedures xp_execresultset, xp_printstatements, and xp_displayparamstmt.
- Limit SQL Server network exposure and require strong authentication for database logins.
- Review database roles to ensure no unprivileged accounts retain execute rights on these procedures.
Detection
- Monitor SQL Server audit logs for execution of xp_execresultset, xp_printstatements, or xp_displayparamstmt by non-administrative logins.
- Alert on privilege changes or unexpected administrative actions originating from low-privileged database accounts.
- Baseline which accounts can execute extended stored procedures and flag deviations.
This assessment is produced automatically and is not human-reviewed. Verify against the vendor advisory before acting on it.
Affected products
2 vulnerable configurations from NVD's CPE data, grouped by vendor and product.
References
Track CVE-2002-0721 inside VULONE
Watch it alongside the ransomware crews, C2 infrastructure and forum chatter that reference it, query it through the API and pull it into your SIEM over TAXII.
Related vulnerabilities
Same products first, then exploited flaws of the same weakness class.
Source: NIST National Vulnerability Database (record CVE-2002-0721), CISA KEV, FIRST EPSS (scores of 2026-09-26). This page is refreshed as NVD updates the record.