How severe is CVE-2005-2249?

CVE-2005-2249 has a CVSS 2.0 base score of 10.0, rated critical severity.

Is CVE-2005-2249 being actively exploited?

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

What products are affected by CVE-2005-2249?

CVE-2005-2249 affects Jinzora. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2005-2249?

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-2005-2249 published?

CVE-2005-2249 was published on 2005-07-13 and last updated on 2026-06-16.

CVE-2005-2249

CVE-2005-2249 is a critical-severity vulnerability in Jinzora 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: 1% (68th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Jinzora
Published: 2005-07-13
Last modified: 2026-06-16

Description

Multiple unknown vulnerabilities in Jinzora 2.0.1 have unknown impact and attack vectors, possibly involving a PHP file inclusion vulnerability.

Frequently asked questions

What is CVE-2005-2249?: Multiple unknown vulnerabilities in Jinzora 2.0.1 have unknown impact and attack vectors, possibly involving a PHP file inclusion vulnerability.
How severe is CVE-2005-2249?: CVE-2005-2249 has a CVSS 2.0 base score of 10.0, rated critical severity.
Is CVE-2005-2249 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (68th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2005-2249?: CVE-2005-2249 affects Jinzora. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2005-2249?: 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-2005-2249 published?: CVE-2005-2249 was published on 2005-07-13 and last updated on 2026-06-16.

References

Affected products (1)

cpe:2.3:a:jinzora:jinzora:2.0.1:*:*:*:*:*:*:*

More vulnerabilities in Jinzora

CVE-2006-7131 — Critical (CVSS 10.0): PHP remote file inclusion vulnerability in extras/mt.php in Jinzora 2.6 allows remote attackers to execute arbitrary…
CVE-2009-2313 — High (CVSS 7.5): Directory traversal vulnerability in index.php in Jinzora Media Jukebox 2.8 and earlier allows remote attackers to…
CVE-2006-7130 — High (CVSS 7.5): PHP remote file inclusion vulnerability in backend/primitives/cache/media.php in Jinzora 2.1 and earlier allows remote…
CVE-2006-6770 — Medium (CVSS 6.8): Multiple PHP remote file inclusion vulnerabilities in Jinzora Media Jukebox 2.7 and earlier, when register_globals is…

All CVEs affecting Jinzora →