cmsgroovel vulnerabilities and fixes
Recent CVEs affecting cmsgroovel, with upgrade or downgrade steps. 1 tracked.
cmsgroovel has 1 tracked vulnerability, 0 critical. A fixed release or vendor patch exists for 1. Most recent: 2017-03-05. Highest priority: CVE-2017-6480 (score 41/100).
- CVE-2017-6480 MEDIUM 6.1 UPGRADE groovel/cmsgroovel before 3.3.7-beta is vulnerable to a reflected XSS in commons/browser.php (path parameter).
FAQ
How do I fix cmsgroovel 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 cmsgroovel being exploited right now?
None of the tracked cmsgroovel CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which cmsgroovel CVE should I patch first?
CVE-2017-6480 currently ranks highest (41/100): groovel/cmsgroovel before 3.3.7-beta is vulnerable to a reflected XSS in commons/browser.php (path parameter)..