How severe is CVE-2005-0509?

CVE-2005-0509 has a CVSS 2.0 base score of 4.3, rated medium severity.

Is CVE-2005-0509 being actively exploited?

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

What products are affected by CVE-2005-0509?

CVE-2005-0509 primarily affects Microsoft .net Framework. In total, 6 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2005-0509?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2005-0509 published?

CVE-2005-0509 was published on 2005-03-14 and last updated on 2026-06-16.

CVE-2005-0509

CVE-2005-0509 is a medium-severity vulnerability in Microsoft .net Framework with a CVSS 2.0 base score of 4.3. Its EPSS exploit-prediction score of 16% places it in the 97th percentile, indicating an elevated likelihood of exploitation.

Key facts

Severity: Medium (CVSS 2.0 base score 4.3)
EPSS exploit prediction: 16% (97th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Microsoft .net Framework
Published: 2005-03-14
Last modified: 2026-06-16

Description

Multiple cross-site scripting (XSS) vulnerabilities in the Mono 1.0.5 implementation of ASP.NET (.Net) allow remote attackers to inject arbitrary HTML or web script via Unicode representations for ASCII fullwidth characters that are converted to normal ASCII characters, including ">" and "<".

Frequently asked questions

What is CVE-2005-0509?: Multiple cross-site scripting (XSS) vulnerabilities in the Mono 1.0.5 implementation of ASP.NET (.Net) allow remote attackers to inject arbitrary HTML or web script via Unicode representations for ASCII fullwidth characters that are converted to normal ASCII characters, including ">" and "<".
How severe is CVE-2005-0509?: CVE-2005-0509 has a CVSS 2.0 base score of 4.3, rated medium severity.
Is CVE-2005-0509 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 16% (97th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2005-0509?: CVE-2005-0509 primarily affects Microsoft .net Framework. In total, 6 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2005-0509?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2005-0509 published?: CVE-2005-0509 was published on 2005-03-14 and last updated on 2026-06-16.

References

Affected products (6)

cpe:2.3:a:microsoft:.net_framework:1.0:*:*:*:*:*:*:*
cpe:2.3:a:microsoft:.net_framework:1.0:sp1:*:*:*:*:*:*
cpe:2.3:a:microsoft:.net_framework:1.0:sp2:*:*:*:*:*:*
cpe:2.3:a:microsoft:.net_framework:1.1:*:*:*:*:*:*:*
cpe:2.3:a:microsoft:.net_framework:1.1:sp1:*:*:*:*:*:*
cpe:2.3:a:mono:mono:1.0.5:*:*:*:*:*:*:*

More vulnerabilities in Microsoft .net Framework

CVE-2014-4121 — Critical (CVSS 10.0): Microsoft .NET Framework 2.0 SP2, 3.5, 3.5.1, 4, 4.5, 4.5.1, and 4.5.2 does not properly parse internationalized…
CVE-2014-4073 — Critical (CVSS 10.0): Microsoft .NET Framework 2.0 SP2, 3.5, 3.5.1, 4, 4.5, 4.5.1, and 4.5.2 processes unverified data during interaction…
CVE-2014-1806 — Critical (CVSS 10.0): The .NET Remoting implementation in Microsoft .NET Framework 1.1 SP1, 2.0 SP2, 3.5, 3.5.1, 4, 4.5, and 4.5.1 does not…
CVE-2013-0073 — Critical (CVSS 10.0): The Windows Forms (aka WinForms) component in Microsoft .NET Framework 2.0 SP2, 3.5, 3.5.1, 4, and 4.5 does not…
CVE-2008-5100 — Critical (CVSS 10.0): The strong name (SN) implementation in Microsoft .NET Framework 2.0.50727 relies on the digital signature Public Key…
CVE-2002-0369 — Critical (CVSS 10.0): Buffer overflow in ASP.NET Worker Process allows remote attackers to cause a denial of service (restart) and possibly…

All CVEs affecting Microsoft .net Framework →