Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

pyblosxom vulnerabilities and fixes

Recent CVEs affecting pyblosxom, with upgrade or downgrade steps. 2 tracked.

pyblosxom has 2 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 2. Most recent: 2006-06-07. Highest priority: CVE-2006-2880 (score 41/100).

FAQ

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

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

Which pyblosxom CVE should I patch first?

CVE-2006-2880 currently ranks highest (41/100): Cross-site scripting (XSS) vulnerability in the Contributed Packages for PyBlosxom 1.2.2 and earlier allows re.

← Back to latest CVEs