navigate cms vulnerabilities and fixes
Recent CVEs affecting navigate cms, with upgrade or downgrade steps. 5 tracked.
Also searched as: navigatecms.
navigate cms has 5 tracked vulnerabilities, 1 critical. A fixed release or vendor patch exists for 0. Most recent: 2022-04-28. Highest priority: CVE-2020-23711 (score 63/100).
- CVE-2022-28117 MEDIUM 4.9 DOWNGRADE A Server-Side Request Forgery (SSRF) in feed_parser class of Navigate CMS v2.9.4 allows remote attackers to fo
- CVE-2021-44299 MEDIUM 5.4 DOWNGRADE A reflected cross-site scripting (XSS) vulnerability in \lib\packages\themes\themes.php of Navigate CMS v2.9.4
- CVE-2021-36455 HIGH 8.8 DOWNGRADE SQL Injection vulnerability in Naviwebs Navigate CMS 2.9 via the quicksearch parameter in \lib\packages\commen
- CVE-2021-36454 MEDIUM 5.4 DOWNGRADE Cross Site Scripting (XSS) vulnerability in Naviwebs Navigate Cms 2.9 via the navigate-quickse parameter to 1)
- CVE-2020-23711 CRITICAL 9.8 DOWNGRADE SQL Injection vulnerability in NavigateCMS 2.9 via the URL encoded GET input category in navigate.php.
FAQ
How do I fix navigate 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 navigate cms being exploited right now?
None of the tracked navigate cms CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which navigate cms CVE should I patch first?
CVE-2020-23711 currently ranks highest (63/100): SQL Injection vulnerability in NavigateCMS 2.9 via the URL encoded GET input category in navigate.php..