PatchTheCVEmaxcms vulnerabilities and fixes
Recent CVEs affecting maxcms, with upgrade or downgrade steps. 5 tracked.
maxcms has 5 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2009-09-25. Highest priority: CVE-2009-3426 (score 49/100).
- CVE-2009-3426 MEDIUM 6.8 DOWNGRADE PHP remote file inclusion vulnerability in includes/file_manager/special.php in MaxCMS 3.11.20b allows remote
- CVE-2009-3425 MEDIUM 5.0 DOWNGRADE Directory traversal vulnerability in includes/inc.thcms_admin_dirtree.php in MaxCMS 3.11.20b allows remote att
- CVE-2009-3424 MEDIUM 6.8 DOWNGRADE Multiple PHP remote file inclusion vulnerabilities in MaxCMS 3.11.20b, when register_globals is enabled, allow
- CVE-2009-1818 HIGH 7.5 DOWNGRADE SQL injection vulnerability in admin/admin_manager.asp in MaxCMS 2.0 allows remote attackers to execute arbitr
- CVE-2009-1764 HIGH 7.5 DOWNGRADE SQL injection vulnerability in inc/ajax.asp in MaxCMS 2.0 allows remote attackers to execute arbitrary SQL com
FAQ
How do I fix maxcms 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 maxcms being exploited right now?
None of the tracked maxcms CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which maxcms CVE should I patch first?
CVE-2009-3426 currently ranks highest (49/100): PHP remote file inclusion vulnerability in includes/file_manager/special.php in MaxCMS 3.11.20b allows remote .