Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

noname cms vulnerabilities and fixes

Recent CVEs affecting noname cms, with upgrade or downgrade steps. 1 tracked.

Also searched as: nonamecms.

noname cms has 1 tracked vulnerability, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2009-02-09. Highest priority: CVE-2008-6093 (score 44/100).

FAQ

How do I fix noname 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 noname cms being exploited right now?

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

Which noname cms CVE should I patch first?

CVE-2008-6093 currently ranks highest (44/100): SQL injection vulnerability in index.php in Noname CMS 1.0, when magic_quotes_gpc is disabled, allows remote a.

← Back to latest CVEs