sparkleblog vulnerabilities and fixes
Recent CVEs affecting sparkleblog, with upgrade or downgrade steps. 1 tracked.
sparkleblog has 1 tracked vulnerability, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2005-10-30. Highest priority: CVE-2005-3367 (score 32/100).
- CVE-2005-3367 MEDIUM 4.3 DOWNGRADE Cross-site scripting (XSS) vulnerability in journal.php in SparkleBlog 2.1 allows remote attackers to inject a
FAQ
How do I fix sparkleblog 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 sparkleblog being exploited right now?
None of the tracked sparkleblog CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which sparkleblog CVE should I patch first?
CVE-2005-3367 currently ranks highest (32/100): Cross-site scripting (XSS) vulnerability in journal.php in SparkleBlog 2.1 allows remote attackers to inject a.