vbook vulnerabilities and fixes
Recent CVEs affecting vbook, with upgrade or downgrade steps. 4 tracked.
vbook has 4 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2010-06-11. Highest priority: CVE-2006-1563 (score 46/100).
- CVE-2009-4890 MEDIUM 4.3 DOWNGRADE Multiple cross-site scripting (XSS) vulnerabilities in the login application in vBook 4.2.17 allow remote atta
- 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
FAQ
How do I fix vbook 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 vbook being exploited right now?
None of the tracked vbook CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which vbook CVE should I patch first?
CVE-2006-1563 currently ranks highest (46/100): Direct static code injection vulnerability in config.php in vscripts (aka Kuba Kunkiewicz) [V]Book (aka VBook).