Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

bluecube cms vulnerabilities and fixes

Recent CVEs affecting bluecube cms, with upgrade or downgrade steps. 1 tracked.

Also searched as: bluecubecms.

bluecube cms has 1 tracked vulnerability, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2009-02-03. Highest priority: CVE-2008-6026 (score 47/100).

FAQ

How do I fix bluecube 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 bluecube cms being exploited right now?

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

Which bluecube cms CVE should I patch first?

CVE-2008-6026 currently ranks highest (47/100): SQL injection vulnerability in tienda.php in BlueCUBE CMS allows remote attackers to execute arbitrary SQL com.

← Back to latest CVEs