CVE-2005-2249

NONECVSS 0.0

0.0

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

CVSS v3: —
EG Score: —
EPSS: 64.5%
KEV: Not listed

Published

July 13, 2005

Last Modified

April 16, 2026

References (4)

cve@mitrehttp://freshmeat.net/projects/jinzora/?branch_id=43140&release_id=200390
cve@mitrehttp://secunia.com/advisories/15952
af854a3a-2127-422b-91ae-364da2661108http://freshmeat.net/projects/jinzora/?branch_id=43140&release_id=200390
af854a3a-2127-422b-91ae-364da2661108http://secunia.com/advisories/15952

Data Freshness Timeline

(refreshed 11× in last 7d / 18× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-05-29 13:40 UTCepss_batch
2026-05-29 13:40 UTCepss_batch
2026-05-28 13:42 UTCepss_batch
2026-05-28 13:42 UTCepss_batch
2026-05-28 13:42 UTCepss_batch
2026-05-27 13:37 UTCepss_batch
2026-05-26 13:41 UTCepss_batch
2026-05-26 13:41 UTCepss_batch
2026-05-26 07:16 UTCepss_batch
2026-05-26 07:16 UTCepss_batch
2026-05-24 16:42 UTCepss_batch
2026-05-22 21:15 UTCepss_batch
2026-05-21 22:38 UTCepss_batch
2026-05-20 22:36 UTCepss_batch
2026-05-20 22:36 UTCepss_batch
2026-05-20 11:20 UTCepss_batch
2026-05-20 11:20 UTCepss_batch
2026-05-18 21:29 UTCepss_batch

Frequently asked(4)

What is CVE-2005-2249?

CVE-2005-2249 is a none vulnerability published on July 13, 2005. Multiple unknown vulnerabilities in Jinzora 2.0.1 have unknown impact and attack vectors, possibly involving a PHP file inclusion vulnerability.

When was CVE-2005-2249 disclosed?

CVE-2005-2249 was first published in the National Vulnerability Database on July 13, 2005, with the most recent update on April 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2005-2249 actively exploited?

CVE-2005-2249 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 64.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

How do I remediate CVE-2005-2249?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2005-2249, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2005-2249

Explore →

Is Your Infrastructure Affected by CVE-2005-2249?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs

CVE-2005-2249

📅 Published

🔄 Last Modified

🔗 References (4)