Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

towerblog vulnerabilities and fixes

Recent CVEs affecting towerblog, with upgrade or downgrade steps. 1 tracked.

towerblog has 1 tracked vulnerability, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2005-04-10. Highest priority: CVE-2005-1055 (score 45/100).

FAQ

How do I fix towerblog 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 towerblog being exploited right now?

None of the tracked towerblog CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.

Which towerblog CVE should I patch first?

CVE-2005-1055 currently ranks highest (45/100): TowerBlog 0.6 and earlier stores the login data file under the web root, which allows remote attackers to obta.

← Back to latest CVEs