vscripts vulnerabilities
Recent CVEs affecting vscripts products. 6 tracked.
vscripts has 6 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2006-03-31. Highest priority: CVE-2006-1545 (score 54/100).
- CVE-2006-1563 HIGH 7.6 DOWNGRADE Direct static code injection vulnerability in config.php in vscripts (aka Kuba Kunkiewicz) [V]Book (aka VBook)
- CVE-2006-1562 MEDIUM 6.8 DOWNGRADE Multiple cross-site scripting (XSS) vulnerabilities in index.php in vscripts (aka Kuba Kunkiewicz) [V]Book (ak
- CVE-2006-1561 MEDIUM 5.1 DOWNGRADE SQL injection vulnerability in index.php in vscripts (aka Kuba Kunkiewicz) [V]Book (aka VBook) 2.0 allows remo
- CVE-2006-1545 HIGH 9.0 DOWNGRADE Direct static code injection vulnerability in admin/config.php in vscripts (aka Kuba Kunkiewicz) VNews 1.2 all
- CVE-2006-1544 MEDIUM 4.3 DOWNGRADE Multiple cross-site scripting (XSS) vulnerabilities in news.php in vscripts (aka Kuba Kunkiewicz) VNews 1.2 al
- CVE-2006-1543 HIGH 7.5 DOWNGRADE Multiple SQL injection vulnerabilities in vscripts (aka Kuba Kunkiewicz) VNews 1.2 allow remote attackers to e
FAQ
How do I fix vscripts 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 vscripts being exploited right now?
None of the tracked vscripts CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which vscripts CVE should I patch first?
CVE-2006-1545 currently ranks highest (54/100): Direct static code injection vulnerability in admin/config.php in vscripts (aka Kuba Kunkiewicz) VNews 1.2 all.