How severe is CVE-2000-0763?

CVE-2000-0763 has a CVSS 2.0 base score of 7.2, rated high severity.

Is CVE-2000-0763 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (66th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2000-0763?

CVE-2000-0763 primarily affects David Bagley Xlock. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2000-0763?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2000-0763 published?

CVE-2000-0763 was published on 2000-10-20 and last updated on 2026-06-16.

CVE-2000-0763

CVE-2000-0763 is a high-severity vulnerability in David Bagley Xlock with a CVSS 2.0 base score of 7.2. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: High (CVSS 2.0 base score 7.2)
EPSS exploit prediction: 1% (66th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: David Bagley Xlock
Published: 2000-10-20
Last modified: 2026-06-16

Description

xlockmore and xlockf do not properly cleanse user-injected format strings, which allows local users to gain root privileges via the -d option.

Frequently asked questions

What is CVE-2000-0763?: xlockmore and xlockf do not properly cleanse user-injected format strings, which allows local users to gain root privileges via the -d option.
How severe is CVE-2000-0763?: CVE-2000-0763 has a CVSS 2.0 base score of 7.2, rated high severity.
Is CVE-2000-0763 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (66th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2000-0763?: CVE-2000-0763 primarily affects David Bagley Xlock. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2000-0763?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2000-0763 published?: CVE-2000-0763 was published on 2000-10-20 and last updated on 2026-06-16.

References

Affected products (2)

cpe:2.3:a:david_bagley:xlock:4.16:*:*:*:*:*:*:*
cpe:2.3:a:david_bagley:xlock:4.16.1:*:*:*:*:*:*:*

More vulnerabilities in David Bagley Xlock

CVE-2000-0455 — Low (CVSS 2.1): Buffer overflow in xlockmore xlock program version 4.16 and earlier allows local users to read sensitive data from…

All CVEs affecting David Bagley Xlock →