How severe is CVE-2002-0539?

CVE-2002-0539 has a CVSS 2.0 base score of 10.0, rated critical severity.

Is CVE-2002-0539 being actively exploited?

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

What products are affected by CVE-2002-0539?

CVE-2002-0539 primarily affects Demarc Security Puresecure. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2002-0539?

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

When was CVE-2002-0539 published?

CVE-2002-0539 was published on 2002-07-03 and last updated on 2026-06-16.

CVE-2002-0539

CVE-2002-0539 is a critical-severity vulnerability in Demarc Security Puresecure with a CVSS 2.0 base score of 10.0. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: Critical (CVSS 2.0 base score 10.0)
EPSS exploit prediction: 2% (79th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Demarc Security Puresecure
Published: 2002-07-03
Last modified: 2026-06-16

Description

Demarc PureSecure 1.05 allows remote attackers to gain administrative privileges via a SQL injection attack in a session ID that is stored in the s_key cookie.

Frequently asked questions

What is CVE-2002-0539?: Demarc PureSecure 1.05 allows remote attackers to gain administrative privileges via a SQL injection attack in a session ID that is stored in the s_key cookie.
How severe is CVE-2002-0539?: CVE-2002-0539 has a CVSS 2.0 base score of 10.0, rated critical severity.
Is CVE-2002-0539 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (79th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2002-0539?: CVE-2002-0539 primarily affects Demarc Security Puresecure. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2002-0539?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2002-0539 published?: CVE-2002-0539 was published on 2002-07-03 and last updated on 2026-06-16.

References

Affected products (2)

cpe:2.3:a:demarc_security:puresecure:1.0.5_for_unix:*:*:*:*:*:*:*
cpe:2.3:a:demarc_security:puresecure:1.0.5_for_windows:*:*:*:*:*:*:*

More vulnerabilities in Demarc Security Puresecure

CVE-2003-0340 — High (CVSS 7.5): Demarc Puresecure 1.6 stores authentication information for the logging server in plaintext, which allows attackers to…

All CVEs affecting Demarc Security Puresecure →