Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

d2kblog vulnerabilities and fixes

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

d2kblog has 2 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2006-03-09. Highest priority: CVE-2006-1123 (score 60/100).

FAQ

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

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

Which d2kblog CVE should I patch first?

CVE-2006-1123 currently ranks highest (60/100): SQL injection vulnerability in D2KBlog 1.0.3 and earlier allows remote attackers to execute arbitrary SQL comm.

← Back to latest CVEs