dingfanzu cms vulnerabilities and fixes
Recent CVEs affecting dingfanzu cms, with upgrade or downgrade steps. 6 tracked.
Also searched as: dingfanzucms.
dingfanzu cms has 6 tracked vulnerabilities, 1 critical. A fixed release or vendor patch exists for 0. Most recent: 2024-11-08. Highest priority: CVE-2024-50966 (score 42/100).
- CVE-2024-50966 CRITICAL 9.3 DOWNGRADE dingfanzu CMS V1.0 was discovered to contain a Cross-Site Request Forgery (CSRF) via the component /admin/doAd
- CVE-2024-48758 MEDIUM 6.1 DOWNGRADE dingfanzu CMS V1.0 was discovered to contain a Cross-Site Request Forgery (CSRF) via the addPro parameter of t
- CVE-2024-48291 MEDIUM 6.3 DOWNGRADE dingfanzu CMS 1.0 was discovered to contain a Cross-Site Request Forgery (CSRF) via /admin/doAdminAction.php?a
- CVE-2024-48191 MEDIUM 6.3 DOWNGRADE dingfanzu CMS 1.0 was discovered to contain a Cross-Site Request Forgery (CSRF) via the component /admin/doAdm
- CVE-2024-46600 MEDIUM 4.7 DOWNGRADE dingfanzu CMS 1.0 was discovered to contain a Cross-Site Request Forgery (CSRF) vulnerability via /admin/doAdm
- CVE-2024-46485 MEDIUM 6.3 DOWNGRADE dingfanzu CMS 1.0 was discovered to contain a Cross-Site Request Forgery (CSRF) via /admin/doAdminAction.php?a
FAQ
How do I fix dingfanzu 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 dingfanzu cms being exploited right now?
None of the tracked dingfanzu cms CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which dingfanzu cms CVE should I patch first?
CVE-2024-50966 currently ranks highest (42/100): dingfanzu CMS V1.0 was discovered to contain a Cross-Site Request Forgery (CSRF) via the component /admin/doAd.