PatchTheCVEvcard vulnerabilities and fixes
Recent CVEs affecting vcard, with upgrade or downgrade steps. 6 tracked.
vcard has 6 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2009-10-26. Highest priority: CVE-2005-3332 (score 52/100).
- CVE-2009-3779 MEDIUM 4.3 DOWNGRADE Cross-site scripting (XSS) vulnerability in vCard 5.x before 5.x-1.4 and 6.x before 6.x-1.3, a module for Drup
- CVE-2006-3474 HIGH 7.5 DOWNGRADE Multiple SQL injection vulnerabilities in Belchior Foundry vCard PRO allow remote attackers to execute arbitra
- CVE-2006-2810 MEDIUM 6.8 DOWNGRADE Multiple cross-site scripting (XSS) vulnerabilities in Belchior Foundry vCard 2.9 allow remote attackers to in
- CVE-2006-1230 MEDIUM 4.3 DOWNGRADE Multiple cross-site scripting (XSS) vulnerabilities in create.php in vCard 2.x allow remote attackers to injec
- CVE-2005-3332 HIGH 7.5 DOWNGRADE PHP remote file include vulnerability in admin/define.inc.php in Belchior Foundry vCard 2.9 allows remote atta
- CVE-2004-1828 MEDIUM 5.0 DOWNGRADE Vcard 2.9 and possibly other versions does not require authorization to run uninstall.php, which could allow r
FAQ
How do I fix vcard 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 vcard being exploited right now?
None of the tracked vcard CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which vcard CVE should I patch first?
CVE-2005-3332 currently ranks highest (52/100): PHP remote file include vulnerability in admin/define.inc.php in Belchior Foundry vCard 2.9 allows remote atta.