PatchTheCVEblog cms vulnerabilities
Recent CVEs affecting blog cms products. 3 tracked.
blog cms has 3 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2008-01-25. Highest priority: CVE-2008-0360 (score 47/100).
- CVE-2008-0450 HIGH 7.5 DOWNGRADE Multiple PHP remote file inclusion vulnerabilities in BLOG:CMS 4.2.1.c allow remote attackers to execute arbit
- CVE-2008-0360 HIGH 7.5 DOWNGRADE Multiple SQL injection vulnerabilities in BLOG:CMS 4.2.1b allow remote attackers to execute arbitrary SQL comm
- CVE-2008-0359 MEDIUM 4.3 DOWNGRADE Multiple cross-site scripting (XSS) vulnerabilities in BLOG:CMS 4.2.1b allow remote attackers to inject arbitr
FAQ
How do I fix blog 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 blog cms being exploited right now?
None of the tracked blog cms CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which blog cms CVE should I patch first?
CVE-2008-0360 currently ranks highest (47/100): Multiple SQL injection vulnerabilities in BLOG:CMS 4.2.1b allow remote attackers to execute arbitrary SQL comm.