PatchTheCVEcpcommerce vulnerabilities and fixes
Recent CVEs affecting cpcommerce, with upgrade or downgrade steps. 4 tracked.
cpcommerce has 4 tracked vulnerabilities, 1 critical. A fixed release or vendor patch exists for 3. Most recent: 2009-06-05. Highest priority: CVE-2009-1936 (score 69/100).
- CVE-2009-1936 CRITICAL 9.8 UPGRADE _functions.php in cpCommerce 1.2.x, possibly including 1.2.9, sends a redirect but does not exit when it is ca
- CVE-2009-1345 HIGH 7.5 DOWNGRADE SQL injection vulnerability in document.php in cpCommerce 1.2.8 allows remote attackers to execute arbitrary S
- CVE-2008-4637 MEDIUM 4.3 UPGRADE Cross-site scripting (XSS) vulnerability in cpCommerce before 1.2.4 allows remote attackers to inject arbitrar
- CVE-2008-4121 MEDIUM 4.3 UPGRADE Multiple cross-site scripting (XSS) vulnerabilities in cpCommerce before 1.2.4 allow remote attackers to injec
FAQ
How do I fix cpcommerce 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 cpcommerce being exploited right now?
None of the tracked cpcommerce CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which cpcommerce CVE should I patch first?
CVE-2009-1936 currently ranks highest (69/100): _functions.php in cpCommerce 1.2.x, possibly including 1.2.9, sends a redirect but does not exit when it is ca.