How severe is CVE-2008-5646?

CVE-2008-5646 has a CVSS 2.0 base score of 7.5, rated high severity.

Is CVE-2008-5646 being actively exploited?

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

What products are affected by CVE-2008-5646?

CVE-2008-5646 primarily affects Trac. In total, 31 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2008-5646?

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-2008-5646 published?

CVE-2008-5646 was published on 2008-12-17 and last updated on 2026-06-16.

CVE-2008-5646

CVE-2008-5646 is a high-severity vulnerability in Trac with a CVSS 2.0 base score of 7.5. 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.5)
EPSS exploit prediction: 1% (65th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Trac
Published: 2008-12-17
Last modified: 2026-06-16

Description

Unspecified vulnerability in Trac before 0.11.2 allows attackers to cause a denial of service via unknown attack vectors related to "certain wiki markup."

Frequently asked questions

What is CVE-2008-5646?: Unspecified vulnerability in Trac before 0.11.2 allows attackers to cause a denial of service via unknown attack vectors related to "certain wiki markup."
How severe is CVE-2008-5646?: CVE-2008-5646 has a CVSS 2.0 base score of 7.5, rated high severity.
Is CVE-2008-5646 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (65th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2008-5646?: CVE-2008-5646 primarily affects Trac. In total, 31 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2008-5646?: 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-2008-5646 published?: CVE-2008-5646 was published on 2008-12-17 and last updated on 2026-06-16.

References

Affected products (31)

cpe:2.3:a:trac:trac:*:*:*:*:*:*:*:*
cpe:2.3:a:trac:trac:0.5:*:*:*:*:*:*:*
cpe:2.3:a:trac:trac:0.5.1:*:*:*:*:*:*:*
cpe:2.3:a:trac:trac:0.5.2:*:*:*:*:*:*:*
cpe:2.3:a:trac:trac:0.6:*:*:*:*:*:*:*
cpe:2.3:a:trac:trac:0.6.1:*:*:*:*:*:*:*
cpe:2.3:a:trac:trac:0.7:*:*:*:*:*:*:*
cpe:2.3:a:trac:trac:0.7.1:*:*:*:*:*:*:*
cpe:2.3:a:trac:trac:0.8:*:*:*:*:*:*:*
cpe:2.3:a:trac:trac:0.8.1:*:*:*:*:*:*:*
cpe:2.3:a:trac:trac:0.8.2:*:*:*:*:*:*:*
cpe:2.3:a:trac:trac:0.8.3:*:*:*:*:*:*:*
cpe:2.3:a:trac:trac:0.8.4:*:*:*:*:*:*:*
cpe:2.3:a:trac:trac:0.9:*:*:*:*:*:*:*
cpe:2.3:a:trac:trac:0.9:b1:*:*:*:*:*:*
cpe:2.3:a:trac:trac:0.9:b2:*:*:*:*:*:*
cpe:2.3:a:trac:trac:0.9.1:*:*:*:*:*:*:*
cpe:2.3:a:trac:trac:0.9.2:*:*:*:*:*:*:*
cpe:2.3:a:trac:trac:0.9.3:*:*:*:*:*:*:*
cpe:2.3:a:trac:trac:0.9.4:*:*:*:*:*:*:*
cpe:2.3:a:trac:trac:0.9.5:*:*:*:*:*:*:*
cpe:2.3:a:trac:trac:0.9.6:*:*:*:*:*:*:*
cpe:2.3:a:trac:trac:0.10:*:*:*:*:*:*:*
cpe:2.3:a:trac:trac:0.10.1:*:*:*:*:*:*:*
cpe:2.3:a:trac:trac:0.10.2:*:*:*:*:*:*:*
cpe:2.3:a:trac:trac:0.10.3:*:*:*:*:*:*:*
cpe:2.3:a:trac:trac:0.10.3.1:*:*:*:*:*:*:*
cpe:2.3:a:trac:trac:0.10.4:*:*:*:*:*:*:*
cpe:2.3:a:trac:trac:0.10.5:*:*:*:*:*:*:*
cpe:2.3:a:trac:trac:0.11:*:*:*:*:*:*:*
cpe:2.3:a:trac:trac:0.11.2:*:*:*:*:*:*:*

More vulnerabilities in Trac

CVE-2008-5647 — Medium (CVSS 5.0): Unspecified vulnerability in the HTML sanitizer filter in Trac before 0.11.2 allows attackers to conduct phishing…

All CVEs affecting Trac →