Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

jupiter cms vulnerabilities and fixes

Recent CVEs affecting jupiter cms, with upgrade or downgrade steps. 14 tracked.

Also searched as: jupitercms.

jupiter cms has 14 tracked vulnerabilities, 1 critical. A fixed release or vendor patch exists for 1. Most recent: 2007-02-16. Highest priority: CVE-2006-4428 (score 67/100).

FAQ

How do I fix jupiter cms vulnerabilities?

Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.

Is jupiter cms being exploited right now?

None of the tracked jupiter cms CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.

Which jupiter cms CVE should I patch first?

CVE-2006-4428 currently ranks highest (67/100): PHP remote file inclusion vulnerability in index.php in Jupiter CMS 1.1.5 allows remote attackers to execute a.

RSS feed for jupiter cms · ← Back to latest CVEs