sagecrm vulnerabilities and fixes

Recent CVEs affecting sagecrm, with upgrade or downgrade steps. 2 tracked.

sagecrm has 2 tracked vulnerabilities, 1 critical. A fixed release or vendor patch exists for 0. Most recent: 2017-02-02. Highest priority: CVE-2017-5219 (score 61/100).

• CVE-2017-5219 CRITICAL 9.8 DOWNGRADE An issue was discovered in SageCRM 7.x before 7.3 SP3
• CVE-2017-5218 HIGH 8.8 DOWNGRADE A SQL Injection issue was discovered in SageCRM 7.x before 7.3 SP3

FAQ

How do I fix sagecrm 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 sagecrm being exploited right now?

None of the tracked sagecrm CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.

Which sagecrm CVE should I patch first?

CVE-2017-5219 currently ranks highest (61/100): An issue was discovered in SageCRM 7.x before 7.3 SP3.

← Back to latest CVEs