PatchTheCVEgoople cms vulnerabilities
Recent CVEs affecting goople cms products. 4 tracked.
goople cms has 4 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 1. Most recent: 2009-02-11. Highest priority: CVE-2008-6118 (score 53/100).
- CVE-2009-0121 HIGH 7.5 DOWNGRADE SQL injection vulnerability in frontpage.php in Goople CMS 1.8.2 allows remote attackers to execute arbitrary
- CVE-2009-0111 HIGH 7.5 UPGRADE SQL injection vulnerability in frontpage.php in Goople CMS 1.8.2 and earlier allows remote attackers to execut
- CVE-2008-6119 HIGH 7.5 DOWNGRADE Static code injection vulnerability in gooplecms/admin/account/action/editpass.php in Goople CMS 1.7 allows re
- CVE-2008-6118 HIGH 7.5 DOWNGRADE win/content/upload.php in Goople CMS 1.7 allows remote attackers to bypass authentication and gain administrat
FAQ
How do I fix goople 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 goople cms being exploited right now?
None of the tracked goople cms CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which goople cms CVE should I patch first?
CVE-2008-6118 currently ranks highest (53/100): win/content/upload.php in Goople CMS 1.7 allows remote attackers to bypass authentication and gain administrat.