sendcard vulnerabilities and fixes
Recent CVEs affecting sendcard, with upgrade or downgrade steps. 6 tracked.
sendcard has 6 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 4. Most recent: 2007-06-06. Highest priority: CVE-2007-3082 (score 54/100).
- CVE-2007-3082 HIGH 7.8 UPGRADE Directory traversal vulnerability in sendcard.php in Sendcard 3.4.1 and earlier allows remote attackers to inc
- CVE-2007-3059 MEDIUM 5.0 DOWNGRADE SendCard 3.3.0 allows remote attackers to obtain sensitive information via an invalid sc_language parameter to
- CVE-2007-2472 MEDIUM 4.3 UPGRADE Cross-site scripting (XSS) vulnerability in sendcard.php in Sendcard 3.4.1 and earlier allows remote attackers
- CVE-2007-2471 MEDIUM 5.0 UPGRADE Directory traversal vulnerability in sendcard.php in Sendcard 3.4.1 and earlier allows remote attackers to rea
- CVE-2006-1006 HIGH 7.5 UPGRADE Multiple SQL injection vulnerabilities in sendcard.php in sendcard before 3.3.0 allow remote attackers to exec
- CVE-2005-2404 HIGH 7.5 DOWNGRADE SQL injection vulnerability in sendcard.php in Sendcard 3.2.3 allows remote attackers to execute arbitrary SQL
FAQ
How do I fix sendcard 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 sendcard being exploited right now?
None of the tracked sendcard CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which sendcard CVE should I patch first?
CVE-2007-3082 currently ranks highest (54/100): Directory traversal vulnerability in sendcard.php in Sendcard 3.4.1 and earlier allows remote attackers to inc.