sweetrice vulnerabilities and fixes
Recent CVEs affecting sweetrice, with upgrade or downgrade steps. 4 tracked.
sweetrice has 4 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2015-01-03. Highest priority: CVE-2010-5317 (score 48/100).
- CVE-2011-3804 MEDIUM 5.0 DOWNGRADE SweetRice 0.7.1 allows remote attackers to obtain sensitive information via a direct request to a .php file, w
- CVE-2010-5318 MEDIUM 4.3 DOWNGRADE The password-reset feature in as/index.php in SweetRice CMS before 0.6.7.1 allows remote attackers to modify t
- CVE-2010-5317 HIGH 7.5 DOWNGRADE Multiple SQL injection vulnerabilities in index.php in SweetRice CMS before 0.6.7.1 allow remote attackers to
- CVE-2010-5316 MEDIUM 4.3 DOWNGRADE Cross-site scripting (XSS) vulnerability in as/index.php in SweetRice CMS before 0.6.7.1 allows remote attacke
FAQ
How do I fix sweetrice 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 sweetrice being exploited right now?
None of the tracked sweetrice CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which sweetrice CVE should I patch first?
CVE-2010-5317 currently ranks highest (48/100): Multiple SQL injection vulnerabilities in index.php in SweetRice CMS before 0.6.7.1 allow remote attackers to .