How severe is CVE-2000-0402?

No CVSS score has been assigned to CVE-2000-0402 yet. Review the advisory details and affected package list to assess your exposure.

Which products are affected by CVE-2000-0402?

CVE-2000-0402 affects the following products: microsoft sql server.

How do I patch CVE-2000-0402?

No patch has shipped for CVE-2000-0402 yet — track the microsoft sql server advisory for a fixed release and apply the workarounds below in the meantime.

How do I detect CVE-2000-0402 across my infrastructure?

Inventory every microsoft sql server deployment and check each version against the affected-products list above.

How do I mitigate CVE-2000-0402 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands. Alongside that, restrict the management interface to trusted networks and apply the vendor's recommended configuration mitigations.

Is CVE-2000-0402 actively exploited in the wild?

Yes. There are 4 known exploit references for CVE-2000-0402, including 2 documented proof-of-concept exploits on Exploit-DB and 2 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2000-0402?

CVE-2000-0402 has an EPSS (Exploit Prediction Scoring System) score of 90.6%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Which products and versions are affected by CVE-2000-0402?

CVE-2000-0402 affects microsoft sql server (1 version, e.g. 7.0). Check the affected-products list on this page against your deployed version to confirm exposure.

When was CVE-2000-0402 published, and has it been updated?

CVE-2000-0402 was published on May 30, 2000 and was last updated on June 16, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

Not in CISA KEV

CVE-2000-0402 — Sql Server

CVE-2000-0402 is a security vulnerability in microsoft sql server. 4 public exploit references exist, so weaponization risk is real. No vendor fix is recorded yet; mitigation options are listed below.

The Mixed Mode authentication capability in Microsoft SQL Server 7.0 stores the System Administrator (sa) account in plaintext in a log file which is readable by any user, aka the "SQL…

Published

May 30, 2000

Updated

Jun 16, 2026

Affected

1 product

Patched

See advisory

Exploits

4 known

Exploitation data as of Oct 27, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

90.6%probability of exploitation in next 30 days

Very High Risk0.00%

Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Description

The Mixed Mode authentication capability in Microsoft SQL Server 7.0 stores the System Administrator (sa) account in plaintext in a log file which is readable by any user, aka the "SQL Server 7.0 Service Pack Password" vulnerability.

Affected Products

1 product · 3 configurations

Application

sql servermicrosoft

1 version

7.0

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-16394remotewindows✓ Verified

Microsoft SQL Server - Payload Execution (via SQL Injection) (Metasploit)

by Metasploit · Feb 8, 2011

Exploit-DB Source

EDB-16395remotewindows✓ Verified

Microsoft SQL Server - Payload Execution (Metasploit)

by Metasploit · Dec 21, 2010

Exploit-DB Source

Detection & mitigation playbook

Vendor / appliance

Detect
Inventory every microsoft sql server deployment and check each version against the affected-products list above.
Remediation status
No patch has shipped for CVE-2000-0402 yet — track the microsoft sql server advisory for a fixed release and apply the workarounds below in the meantime.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands. Alongside that, restrict the management interface to trusted networks and apply the vendor's recommended configuration mitigations.

Frequently Asked Questions

O3 Security · Runtime Protection

Is CVE-2000-0402 being exploited in your environment?

Detect and block the exploit chain at execution, on systems you cannot patch yet.

Protect my workloads How runtime protection works