mangoswebv4 project vulnerabilities
Recent CVEs affecting mangoswebv4 project products. 6 tracked.
mangoswebv4 project has 6 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 1. Most recent: 2017-03-11. Highest priority: CVE-2017-6478 (score 48/100).
- CVE-2017-6812 MEDIUM 6.1 DOWNGRADE paintballrefjosh/MaNGOSWebV4 4.0.8 is vulnerable to a reflected XSS in inc/admin/template_files/admin.vote.php
- CVE-2017-6811 MEDIUM 6.1 DOWNGRADE paintballrefjosh/MaNGOSWebV4 4.0.8 is vulnerable to a reflected XSS in inc/admin/template_files/admin.shop.php
- CVE-2017-6810 MEDIUM 6.1 DOWNGRADE paintballrefjosh/MaNGOSWebV4 4.0.8 is vulnerable to a reflected XSS in inc/admin/template_files/admin.fplinks.
- CVE-2017-6809 MEDIUM 6.1 DOWNGRADE paintballrefjosh/MaNGOSWebV4 4.0.8 is vulnerable to a reflected XSS in inc/admin/template_files/admin.donate.p
- CVE-2017-6808 MEDIUM 6.1 DOWNGRADE paintballrefjosh/MaNGOSWebV4 4.0.8 is vulnerable to a reflected XSS in inc/admin/template_files/admin.faq.php
- CVE-2017-6478 MEDIUM 6.1 UPGRADE paintballrefjosh/MaNGOSWebV4 before 4.0.8 is vulnerable to a reflected XSS in install/index.php (step paramete
FAQ
How do I fix mangoswebv4 project 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 mangoswebv4 project being exploited right now?
None of the tracked mangoswebv4 project CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which mangoswebv4 project CVE should I patch first?
CVE-2017-6478 currently ranks highest (48/100): paintballrefjosh/MaNGOSWebV4 before 4.0.8 is vulnerable to a reflected XSS in install/index.php (step paramete.