PatchTheCVEbtitracker vulnerabilities and fixes
Recent CVEs affecting btitracker, with upgrade or downgrade steps. 4 tracked.
btitracker has 4 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 3. Most recent: 2008-08-26. Highest priority: CVE-2008-3784 (score 50/100).
- CVE-2008-3784 HIGH 7.5 UPGRADE UPGRADE SQL injection vulnerability in scrape.php in BtiTracker 1.4.7 and earlier and xBtiTracker 2.0.542 and earlier
- CVE-2007-5986 HIGH 7.5 UPGRADE SQL injection vulnerability in include/functions.php in BtiTracker before 1.4.5 allows remote attackers to exe
- CVE-2006-7159 MEDIUM 6.4 DOWNGRADE DOWNGRADE Directory traversal vulnerability in include/prune_torrents.php in BTI-Tracker 1.3.2 (aka btitracker) allows r
- CVE-2006-6972 HIGH 7.5 UPGRADE SQL injection in torrents.php in BtitTracker 1.3.2 and earlier allows remote attackers to execute arbitrary SQ
FAQ
How do I fix btitracker 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 btitracker being exploited right now?
None of the tracked btitracker CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which btitracker CVE should I patch first?
CVE-2008-3784 currently ranks highest (50/100): SQL injection vulnerability in scrape.php in BtiTracker 1.4.7 and earlier and xBtiTracker 2.0.542 and earlier .