How severe is CVE-2009-2357?

CVE-2009-2357 has a CVSS 2.0 base score of 10.0, rated critical severity.

Is CVE-2009-2357 being actively exploited?

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

What products are affected by CVE-2009-2357?

CVE-2009-2357 affects Yasinkaplan Tekradius. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2009-2357?

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-2009-2357 published?

CVE-2009-2357 was published on 2009-07-07 and last updated on 2026-06-16.

CVE-2009-2357

CVE-2009-2357 is a critical-severity vulnerability in Yasinkaplan Tekradius 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. The underlying weakness is classified as CWE-16.

Key facts

Severity: Critical (CVSS 2.0 base score 10.0)
EPSS exploit prediction: 2% (80th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-16
Affected product: Yasinkaplan Tekradius
Published: 2009-07-07
Last modified: 2026-06-16

Description

The default configuration of TekRADIUS 3.0 uses the sa account to communicate with Microsoft SQL Server, which makes it easier for remote attackers to obtain privileged access to the database and the underlying Windows operating system.

Frequently asked questions

What is CVE-2009-2357?: The default configuration of TekRADIUS 3.0 uses the sa account to communicate with Microsoft SQL Server, which makes it easier for remote attackers to obtain privileged access to the database and the underlying Windows operating system.
How severe is CVE-2009-2357?: CVE-2009-2357 has a CVSS 2.0 base score of 10.0, rated critical severity.
Is CVE-2009-2357 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (80th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2009-2357?: CVE-2009-2357 affects Yasinkaplan Tekradius. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2009-2357?: 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-2009-2357 published?: CVE-2009-2357 was published on 2009-07-07 and last updated on 2026-06-16.

References

Affected products (1)

cpe:2.3:a:yasinkaplan:tekradius:3.0:*:*:*:*:*:*:*

More vulnerabilities in Yasinkaplan Tekradius

CVE-2009-2359 — High (CVSS 7.5): Multiple SQL injection vulnerabilities in TekRADIUS 3.0 allow context-dependent attackers to execute arbitrary SQL…
CVE-2009-2358 — Medium (CVSS 4.6): TekRADIUS 3.0 uses BUILTIN\Users:R permissions for the TekRADIUS.ini file, which allows local users to obtain…

All CVEs affecting Yasinkaplan Tekradius →

Other CWE-16 vulnerabilities

CVE-2013-4316 — Critical (CVSS 10.0): Apache Struts 2.0.0 through 2.3.15.1 enables Dynamic Method Invocation by default, which has unknown impact and attack…
CVE-2013-1221 — Critical (CVSS 10.0): The Tomcat Web Management feature in Cisco Unified Customer Voice Portal (CVP) Software before 9.0.1 ES 11 does not…
CVE-2011-4501 — Critical (CVSS 10.0): The UPnP IGD implementation in Edimax EdiLinux on the Edimax BR-6104K with firmware before 3.25, Edimax 6114Wg,…
CVE-2010-4586 — Critical (CVSS 10.0): The default configuration of Opera before 11.00 enables WebSockets functionality, which has unspecified impact and…
CVE-2010-2977 — Critical (CVSS 10.0): Cisco Unified Wireless Network (UWN) Solution 7.x before 7.0.98.0 does not properly implement TLS and SSL, which has…
CVE-2010-2276 — Critical (CVSS 10.0): The default configuration of the build process in Dojo 0.4.x before 0.4.4, 1.0.x before 1.0.3, 1.1.x before 1.1.2,…

Browse all CWE-16 vulnerabilities →