How severe is CVE-2006-2105?

CVE-2006-2105 has a CVSS 2.0 base score of 5.0, rated medium severity.

Is CVE-2006-2105 being actively exploited?

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

What products are affected by CVE-2006-2105?

CVE-2006-2105 primarily affects Jupiter Cms. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2006-2105?

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

When was CVE-2006-2105 published?

CVE-2006-2105 was published on 2006-04-29 and last updated on 2026-06-16.

CVE-2006-2105

CVE-2006-2105 is a medium-severity vulnerability in Jupiter Cms with a CVSS 2.0 base score of 5.0. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: Medium (CVSS 2.0 base score 5.0)
EPSS exploit prediction: 1% (66th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Jupiter Cms
Published: 2006-04-29
Last modified: 2026-06-16

Description

Directory traversal vulnerability in index.php in Jupiter CMS 1.1.4 and 1.1.5 allows remote attackers to read arbitrary files via ".." sequences terminated by a %00 (null) character in the n parameter.

Frequently asked questions

What is CVE-2006-2105?: Directory traversal vulnerability in index.php in Jupiter CMS 1.1.4 and 1.1.5 allows remote attackers to read arbitrary files via ".." sequences terminated by a %00 (null) character in the n parameter.
How severe is CVE-2006-2105?: CVE-2006-2105 has a CVSS 2.0 base score of 5.0, rated medium severity.
Is CVE-2006-2105 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (66th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2006-2105?: CVE-2006-2105 primarily affects Jupiter Cms. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2006-2105?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2006-2105 published?: CVE-2006-2105 was published on 2006-04-29 and last updated on 2026-06-16.

References

Affected products (2)

cpe:2.3:a:jupiter_cms:jupiter_cms:1.1.4:*:*:*:*:*:*:*
cpe:2.3:a:jupiter_cms:jupiter_cms:1.1.5:*:*:*:*:*:*:*

More vulnerabilities in Jupiter Cms

CVE-2006-4428 — Critical (CVSS 9.8): PHP remote file inclusion vulnerability in index.php in Jupiter CMS 1.1.5 allows remote attackers to execute arbitrary…
CVE-2007-0987 — High (CVSS 7.5): Directory traversal vulnerability in index.php in Jupiter CMS 1.1.5 allows remote attackers to include and execute…
CVE-2007-0971 — High (CVSS 7.5): Multiple SQL injection vulnerabilities in Jupiter CMS 1.1.5 allow remote attackers to execute arbitrary SQL commands…
CVE-2007-0972 — High (CVSS 7.5): Unrestricted file upload vulnerability in modules/emoticons.php in Jupiter CMS 1.1.5 allows remote attackers to upload…
CVE-2006-4876 — High (CVSS 7.5): Multiple SQL injection vulnerabilities in Jupiter CMS allow remote attackers to execute arbitrary SQL commands via (1)…
CVE-2007-0973 — Medium (CVSS 6.8): Multiple cross-site scripting (XSS) vulnerabilities in index.php in Jupiter CMS 1.1.5 allow remote attackers to inject…

All CVEs affecting Jupiter Cms →