PatchTheCVEdilicms vulnerabilities
Recent CVEs affecting dilicms products. 7 tracked.
dilicms has 7 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2019-03-07. Highest priority: CVE-2018-19291 (score 41/100).
- CVE-2019-8440 MEDIUM 4.8 DOWNGRADE An issue was discovered in DiliCMS 2.4.0
- CVE-2019-8439 MEDIUM 5.4 DOWNGRADE An issue was discovered in DiliCMS 2.4.0
- CVE-2019-8438 MEDIUM 4.8 DOWNGRADE An issue was discovered in DiliCMS 2.4.0
- CVE-2018-19291 MEDIUM 6.5 DOWNGRADE An issue was discovered in DiliCMS 2.4.0
- CVE-2018-18210 MEDIUM 6.1 DOWNGRADE XSS exists in DiliCMS 2.4.0 via the admin/index.php/setting/site?tab=site_attachment attachment_url parameter.
- CVE-2018-18209 MEDIUM 6.1 DOWNGRADE XSS exists in DiliCMS 2.4.0 via the admin/index.php/setting/site?tab=site_attachment attachment_type parameter
- CVE-2018-10430 MEDIUM 4.8 DOWNGRADE An issue was discovered in DiliCMS (aka DiligentCMS) 2.4.0
FAQ
How do I fix dilicms 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 dilicms being exploited right now?
None of the tracked dilicms CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which dilicms CVE should I patch first?
CVE-2018-19291 currently ranks highest (41/100): An issue was discovered in DiliCMS 2.4.0.