Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

maxcms vulnerabilities

Recent CVEs affecting maxcms products. 1 tracked.

maxcms has 1 tracked vulnerability, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2009-05-29. Highest priority: CVE-2009-1818 (score 47/100).

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-1818 currently ranks highest (47/100): SQL injection vulnerability in admin/admin_manager.asp in MaxCMS 2.0 allows remote attackers to execute arbitr.

Products

← Back to latest CVEs