no-cms vulnerabilities and fixes

Recent CVEs affecting no-cms, with upgrade or downgrade steps. 3 tracked.

Also searched as: no cms.

no-cms has 3 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2018-12-31. Highest priority: CVE-2018-18868 (score 40/100).

• CVE-2018-19902 MEDIUM 4.8 DOWNGRADE No-CMS 1.1.3 is prone to Persistent XSS via the blog/manage_article "keyword" parameter.
• CVE-2018-19901 MEDIUM 4.8 DOWNGRADE No-CMS 1.1.3 is prone to Persistent XSS via the blog/manage_article/index/ "article_title" parameter.
• CVE-2018-18868 MEDIUM 6.1 DOWNGRADE No-CMS 1.1.3 is prone to Persistent XSS via a contact_us name parameter, as demonstrated by the VG48Z5PqVWname

FAQ

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

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

Which no-cms CVE should I patch first?

CVE-2018-18868 currently ranks highest (40/100): No-CMS 1.1.3 is prone to Persistent XSS via a contact_us name parameter, as demonstrated by the VG48Z5PqVWname.

RSS feed for no-cms · ← Back to latest CVEs