PatchTheCVElokicms vulnerabilities
Recent CVEs affecting lokicms products. 4 tracked.
lokicms has 4 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 2. Most recent: 2009-04-07. Highest priority: CVE-2008-4662 (score 50/100).
- CVE-2008-6643 MEDIUM 5.0 DOWNGRADE LokiCMS 0.3.4 and possibly earlier versions does not properly restrict access to administrative functions, whi
- CVE-2008-5965 MEDIUM 5.0 UPGRADE Directory traversal vulnerability in index.php in LokiCMS 0.3.4 and earlier, when magic_quotes_gpc is disabled
- CVE-2008-4913 MEDIUM 5.0 UPGRADE Directory traversal vulnerability in admin.php in LokiCMS 0.3.3 and earlier allows remote attackers to delete
- CVE-2008-4662 MEDIUM 6.8 DOWNGRADE Directory traversal vulnerability in admin.php in LokiCMS 0.3.4, when magic_quotes_gpc is disabled, allows rem
FAQ
How do I fix lokicms 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 lokicms being exploited right now?
None of the tracked lokicms CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which lokicms CVE should I patch first?
CVE-2008-4662 currently ranks highest (50/100): Directory traversal vulnerability in admin.php in LokiCMS 0.3.4, when magic_quotes_gpc is disabled, allows rem.