How severe is CVE-2006-4876?

CVE-2006-4876 has a CVSS 2.0 base score of 7.5, rated high severity.

Is CVE-2006-4876 being actively exploited?

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

What products are affected by CVE-2006-4876?

CVE-2006-4876 affects Jupiter Cms. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2006-4876?

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-2006-4876 published?

CVE-2006-4876 was published on 2006-09-19 and last updated on 2026-06-16.

CVE-2006-4876

CVE-2006-4876 is a high-severity vulnerability in Jupiter Cms 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: 2% (80th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Jupiter Cms
Published: 2006-09-19
Last modified: 2026-06-16

Description

Multiple SQL injection vulnerabilities in Jupiter CMS allow remote attackers to execute arbitrary SQL commands via (1) the user name during login, or the (2) key or (3) fpwusername parameters in modules/register.

Frequently asked questions

What is CVE-2006-4876?: Multiple SQL injection vulnerabilities in Jupiter CMS allow remote attackers to execute arbitrary SQL commands via (1) the user name during login, or the (2) key or (3) fpwusername parameters in modules/register.
How severe is CVE-2006-4876?: CVE-2006-4876 has a CVSS 2.0 base score of 7.5, rated high severity.
Is CVE-2006-4876 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (80th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2006-4876?: CVE-2006-4876 affects Jupiter Cms. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2006-4876?: 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-2006-4876 published?: CVE-2006-4876 was published on 2006-09-19 and last updated on 2026-06-16.

References

Affected products (1)

cpe:2.3:a:jupiter_cms:jupiter_cms:*:*:*:*:*:*:*:*

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-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…
CVE-2007-0986 — Medium (CVSS 5.1): PHP remote file inclusion vulnerability in index.php in Jupiter CMS 1.1.5, when PHP 5.0.0 or later is used, allows…

All CVEs affecting Jupiter Cms →