Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

max.blog vulnerabilities and fixes

Recent CVEs affecting max.blog, with upgrade or downgrade steps. 2 tracked.

Also searched as: max blog, maxblog.

max.blog has 2 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2009-02-03. Highest priority: CVE-2009-0383 (score 49/100).

FAQ

How do I fix max.blog 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 max.blog being exploited right now?

None of the tracked max.blog CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.

Which max.blog CVE should I patch first?

CVE-2009-0383 currently ranks highest (49/100): delete.php in Max.Blog 1.0.6 does not properly restrict access, which allows remote attackers to delete arbitr.

← Back to latest CVEs