Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

mymagazine magazine \& blog cms vulnerabilities and fixes

Recent CVEs affecting mymagazine magazine \& blog cms, with upgrade or downgrade steps. 1 tracked.

Also searched as: mymagazinemagazine\&blogcms.

mymagazine magazine \& blog cms has 1 tracked vulnerability, 1 critical. A fixed release or vendor patch exists for 0. Most recent: 2017-10-31. Highest priority: CVE-2017-15983 (score 66/100).

FAQ

How do I fix mymagazine magazine \& blog 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 mymagazine magazine \& blog cms being exploited right now?

None of the tracked mymagazine magazine \& blog cms CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.

Which mymagazine magazine \& blog cms CVE should I patch first?

CVE-2017-15983 currently ranks highest (66/100): MyMagazine Magazine & Blog CMS 1.0 allows SQL Injection via the id parameter to admin/admin_process.php for fo.

← Back to latest CVEs