PatchTheCVEphpbugtracker vulnerabilities and fixes
Recent CVEs affecting phpbugtracker, with upgrade or downgrade steps. 7 tracked.
phpbugtracker has 7 tracked vulnerabilities, 2 critical. A fixed release or vendor patch exists for 7. Most recent: 2017-10-06. Highest priority: CVE-2015-2147 (score 63/100).
- CVE-2015-2148 MEDIUM 4.8 UPGRADE Multiple cross-site scripting (XSS) vulnerabilities in Issuetracker phpBugTracker before 1.7.2 allow remote at
- CVE-2015-2147 CRITICAL 9.8 UPGRADE Multiple SQL injection vulnerabilities in Issuetracker phpBugTracker before 1.7.0 allow remote attackers to ex
- CVE-2015-2146 CRITICAL 9.8 UPGRADE Multiple SQL injection vulnerabilities in Issuetracker phpBugTracker before 1.7.0 allow remote attackers to ex
- CVE-2015-2145 MEDIUM 4.8 UPGRADE Multiple cross-site scripting (XSS) vulnerabilities in Issuetracker phpBugTracker before 1.7.0 allow remote at
- CVE-2015-2144 MEDIUM 4.8 UPGRADE Multiple cross-site scripting (XSS) vulnerabilities in Issuetracker phpBugTracker before 1.7.0 allow remote au
- CVE-2015-2143 HIGH 8.8 UPGRADE Multiple cross-site request forgery (CSRF) vulnerabilities in Issuetracker phpBugTracker before 1.7.0 allow re
- CVE-2015-2142 HIGH 8.0 UPGRADE Multiple cross-site request forgery (CSRF) vulnerabilities in Issuetracker phpBugTracker before 1.7.0 allow re
FAQ
How do I fix phpbugtracker 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 phpbugtracker being exploited right now?
None of the tracked phpbugtracker CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which phpbugtracker CVE should I patch first?
CVE-2015-2147 currently ranks highest (63/100): Multiple SQL injection vulnerabilities in Issuetracker phpBugTracker before 1.7.0 allow remote attackers to ex.