PatchTheCVEbti-tracker vulnerabilities
Recent CVEs affecting bti-tracker products. 5 tracked.
bti-tracker has 5 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 4. Most recent: 2007-11-15. Highest priority: CVE-2007-2854 (score 48/100).
- CVE-2007-5988 HIGH 7.5 UPGRADE blocks/shoutbox_block.php in BtiTracker 1.4.4 does not verify user accounts, which allows remote attackers to
- CVE-2007-5987 MEDIUM 6.8 UPGRADE details.php in BtiTracker before 1.4.5, when torrent viewing is disabled for guests, allows remote attackers t
- CVE-2007-5985 MEDIUM 4.3 UPGRADE Multiple cross-site scripting (XSS) vulnerabilities in BtiTracker before 1.4.5 allow remote attackers to injec
- CVE-2007-2854 HIGH 7.5 UPGRADE Multiple SQL injection vulnerabilities in account_change.php in BtiTracker 1.4.1 and earlier allow remote atta
- 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
FAQ
How do I fix bti-tracker 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 bti-tracker being exploited right now?
None of the tracked bti-tracker CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which bti-tracker CVE should I patch first?
CVE-2007-2854 currently ranks highest (48/100): Multiple SQL injection vulnerabilities in account_change.php in BtiTracker 1.4.1 and earlier allow remote atta.