PatchTheCVEoblog vulnerabilities and fixes
Recent CVEs affecting oblog, with upgrade or downgrade steps. 6 tracked.
oblog has 6 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2010-06-25. Highest priority: CVE-2009-4909 (score 48/100).
- CVE-2009-4909 MEDIUM 6.8 MITIGATE admin/index.php in oBlog allows remote attackers to conduct brute-force password guessing attacks via HTTP req
- CVE-2009-4908 MEDIUM 4.3 MITIGATE Multiple cross-site scripting (XSS) vulnerabilities in oBlog allow remote attackers to inject arbitrary web sc
- CVE-2009-4907 MEDIUM 6.8 MITIGATE Multiple cross-site request forgery (CSRF) vulnerabilities in oBlog allow remote attackers to hijack the authe
- CVE-2009-4904 MEDIUM 5.0 MITIGATE article.php in oBlog does not properly restrict comments, which allows remote attackers to cause a denial of s
- CVE-2009-4903 MEDIUM 4.3 MITIGATE Cross-site scripting (XSS) vulnerability in index.php in oBlog allows remote attackers to inject arbitrary web
- CVE-2009-0283 MEDIUM 4.3 MITIGATE Cross-site scripting (XSS) vulnerability in err.asp in Oblog allows remote attackers to inject arbitrary web s
FAQ
How do I fix oblog 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 oblog being exploited right now?
None of the tracked oblog CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which oblog CVE should I patch first?
CVE-2009-4909 currently ranks highest (48/100): admin/index.php in oBlog allows remote attackers to conduct brute-force password guessing attacks via HTTP req.