wheatblog vulnerabilities
Recent CVEs affecting wheatblog products. 6 tracked.
wheatblog has 6 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 3. Most recent: 2007-07-04. Highest priority: CVE-2006-4198 (score 46/100).
- CVE-2007-3557 MEDIUM 6.8 DOWNGRADE SQL injection vulnerability in admin/login.php in Wheatblog (wB) 1.1, when magic_quotes_gpc is disabled, allow
- CVE-2006-7002 MEDIUM 4.3 DOWNGRADE Cross-site scripting (XSS) vulnerability in add_comment.php in Wheatblog (wB) 1.1 allows remote attackers to i
- CVE-2006-5922 MEDIUM 5.0 UPGRADE index.php in Wheatblog (wB) allows remote attackers to obtain sensitive information via certain values of the
- CVE-2006-5921 MEDIUM 5.8 UPGRADE Multiple cross-site scripting (XSS) vulnerabilities in add_comment.php in Wheatblog (wB) allow remote attacker
- CVE-2006-5195 MEDIUM 6.8 DOWNGRADE Multiple cross-site scripting (XSS) vulnerabilities in Wheatblog 1.0 and 1.1 allow remote attackers to inject
- CVE-2006-4198 MEDIUM 5.1 UPGRADE PHP remote file inclusion vulnerability in includes/session.php in Wheatblog (wB) 1.1 and earlier, when regist
FAQ
How do I fix wheatblog 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 wheatblog being exploited right now?
None of the tracked wheatblog CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which wheatblog CVE should I patch first?
CVE-2006-4198 currently ranks highest (46/100): PHP remote file inclusion vulnerability in includes/session.php in Wheatblog (wB) 1.1 and earlier, when regist.