tunez vulnerabilities and fixes
Recent CVEs affecting tunez, with upgrade or downgrade steps. 3 tracked.
tunez has 3 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2005-11-26. Highest priority: CVE-2005-3833 (score 48/100).
- CVE-2005-3834 MEDIUM 4.3 DOWNGRADE Cross-site scripting (XSS) vulnerability in search.php in Tunez 1.21 and earlier allows remote attackers to in
- CVE-2005-3833 HIGH 7.5 DOWNGRADE SQL injection vulnerability in songinfo.php in Tunez 1.21 and earlier allows remote attackers to execute arbit
- CVE-2004-2349 HIGH 7.5 DOWNGRADE Multiple SQL injection vulnerabilities in Tunez before 1.20-pre2 allow remote attackers to execute arbitrary S
FAQ
How do I fix tunez 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 tunez being exploited right now?
None of the tracked tunez CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which tunez CVE should I patch first?
CVE-2005-3833 currently ranks highest (48/100): SQL injection vulnerability in songinfo.php in Tunez 1.21 and earlier allows remote attackers to execute arbit.