PatchTheCVEmyblog vulnerabilities
Recent CVEs affecting myblog products. 7 tracked.
myblog has 7 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 3. Most recent: 2010-04-26. Highest priority: CVE-2007-2081 (score 55/100).
- CVE-2010-1540 MEDIUM 5.0 DOWNGRADE Directory traversal vulnerability in index.php in the MyBlog (com_myblog) component 3.0.329 for Joomla! allows
- CVE-2008-6193 MEDIUM 5.0 MITIGATE Sam Crew MyBlog stores passwords in cleartext in a MySQL database, which allows context-dependent attackers to
- CVE-2008-4341 HIGH 7.5 UPGRADE add.php in MyBlog 0.9.8 and earlier allows remote attackers to bypass authentication and gain administrative a
- CVE-2008-2963 MEDIUM 6.8 MITIGATE Multiple SQL injection vulnerabilities in MyBlog allow remote attackers to execute arbitrary SQL commands via
- CVE-2008-2962 MEDIUM 4.3 MITIGATE Multiple cross-site scripting (XSS) vulnerabilities in MyBlog allow remote attackers to inject arbitrary web s
- CVE-2007-2082 MEDIUM 6.5 UPGRADE Direct static code injection vulnerability in admin/settings.php in MyBlog 0.9.8 and earlier allows remote aut
- CVE-2007-2081 HIGH 7.5 UPGRADE MyBlog 0.9.8 and earlier allows remote attackers to bypass authentication requirements via the admin cookie pa
FAQ
How do I fix myblog 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 myblog being exploited right now?
None of the tracked myblog CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which myblog CVE should I patch first?
CVE-2007-2081 currently ranks highest (55/100): MyBlog 0.9.8 and earlier allows remote attackers to bypass authentication requirements via the admin cookie pa.