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

This month

HIGH 8.8DOWNGRADE

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

A SQL Injection issue was discovered in SageCRM 7.x before 7.3 SP3. The AP_DocumentUI.asp web resource includes Utilityfuncs.js when the file is opened or viewed. This file crafts a SQL statement to identify the database that is to be in use with the current user's session. The database variable can be populated from the URL, and when supplied non-expected characters, can be manipulated to obtain access to the underlying database. The /CRM/Custom

Why this priority

High severity

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

Risk facts

CVSS score	8.8 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	1.5% (top 26%)
CISA exploited list	No
Weakness	CWE-89
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.0 · 7.1 · 7.2 · 7.3 · 7.3 sp1 · 7.3 sp2

Fixed in: no fixed release known

Safe to downgrade to: a release before 7.0

1. Check installed version

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

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

apt-cache madison sagecrm sudo apt install sagecrm=<VERSION_BEFORE_7.0> 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.0> 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-5218?

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

Is CVE-2017-5218 being exploited?

CVE-2017-5218 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-5218 affect?

CVE-2017-5218 affects sagecrm. Severity is high (CVSS 8.8). A SQL Injection issue was discovered in SageCRM 7.x before 7.3 SP3. The AP_DocumentUI.asp web resource includes Utilityfuncs.js when the file is opened or viewed. This file crafts a SQL statement to identify the database that is to be in us

How urgent is CVE-2017-5218?

Priority 49/100. High severity

Related CVEs

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

References

← Back to latest CVEs