CVE-2017-5219: An issue was discovered in SageCRM 7.x before 7.3 SP3

This week

CRITICAL 9.8REMOTEDOWNGRADE

CVE-2017-5219 is a critical-severity flaw (CVSS 9.8) affecting sagecrm. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

An issue was discovered in SageCRM 7.x before 7.3 SP3. The Component Manager functionality, provided by SageCRM, permits additional components to be added to the application to enhance provided functionality. This functionality allows a zip file to be uploaded, containing a valid .ecf component file, which will be extracted to the inf directory outside of the webroot. By creating a zip file containing an empty .ecf file, to pass file-validation c

Why this priority

Critical severity
Remotely exploitable, no login, no user action

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	3.3% (top 12%)
CISA exploited list	No
Weakness	CWE-22
Published	2017-02-02
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: sagecrm

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2017-02-02 07:59 UTCPublished CVE record published
2026-06-17 01:20 UTCUpdated Record last modified

sagecrm sagecrm DOWNGRADE

Affected: 7.3 · 7.3 sp1 · 7.3 sp2

Fixed in: no fixed release known

Safe to downgrade to: a release before 7.3

1. Check installed version

apt-cache policy sagecrm || rpm -q sagecrm || sagecrm --version

2. No fixed release: DOWNGRADE to a release before 7.3 (Debian / Ubuntu)

apt-cache madison sagecrm sudo apt install sagecrm=<VERSION_BEFORE_7.3> sudo apt-mark hold sagecrm

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list sagecrm sudo dnf downgrade sagecrm-<VERSION_BEFORE_7.3> sudo dnf versionlock add sagecrm

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2017-5219?

sagecrm: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2017-5219 being exploited?

CVE-2017-5219 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2017-5219 affect?

CVE-2017-5219 affects sagecrm. Severity is critical (CVSS 9.8). An issue was discovered in SageCRM 7.x before 7.3 SP3. The Component Manager functionality, provided by SageCRM, permits additional components to be added to the application to enhance provided functionality. This functionality allows a zip

How urgent is CVE-2017-5219?

Priority 61/100. Critical severity; Remotely exploitable, no login, no user action

Related CVEs

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

References

← Back to latest CVEs