PatchTheCVEdtracker vulnerabilities and fixes
Recent CVEs affecting dtracker, with upgrade or downgrade steps. 4 tracked.
dtracker has 4 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2017-09-14. Highest priority: CVE-2017-1002007 (score 58/100).
- CVE-2017-1002007 HIGH 7.5 DOWNGRADE Vulnerability in wordpress plugin DTracker v1.5, The code dtracker/save_mail.php doesn't check that the user i
- CVE-2017-1002006 HIGH 7.5 DOWNGRADE Vulnerability in wordpress plugin DTracker v1.5, The code dtracker/save_contact.php doesn't check that the use
- CVE-2017-1002005 HIGH 7.5 DOWNGRADE Vulnerability in wordpress plugin DTracker v1.5, In file ./dtracker/delete.php user input isn't sanitized via
- CVE-2017-1002004 HIGH 7.5 DOWNGRADE Vulnerability in wordpress plugin DTracker v1.5, In file ./dtracker/download.php user input isn't sanitized vi
FAQ
How do I fix dtracker 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 dtracker being exploited right now?
None of the tracked dtracker CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which dtracker CVE should I patch first?
CVE-2017-1002007 currently ranks highest (58/100): Vulnerability in wordpress plugin DTracker v1.5, The code dtracker/save_mail.php doesn't check that the user i.