Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

blusky cms vulnerabilities and fixes

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

Also searched as: bluskycms.

blusky cms has 1 tracked vulnerability, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2009-05-06. Highest priority: CVE-2009-1548 (score 47/100).

FAQ

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

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

Which blusky cms CVE should I patch first?

CVE-2009-1548 currently ranks highest (47/100): SQL injection vulnerability in index.php in BluSky CMS allows remote attackers to execute arbitrary SQL comman.

← Back to latest CVEs