SugarCRM before 10.1.0 (Q3 2020) allows SQL Injection.

published 2020-08-12 6 y ago modified 2026-06-17 4 mo ago also EUVD-2020-9327

cvss: 5.3; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 1.4%; EPSS 1.4% chance of exploitation in 30 days, percentile 73%
public exploits: 0; none known

Patch / fix

fixed in 1

sugarcrm sugarcrm 10.1.0

Exploit prediction

1.44% chance of exploitation in the next 30 days, higher than 73% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

seclists.org http://seclists.org/fulldisclosure/2020/Aug/9 referenced PoC, tagged "exploit" by a source, unverified
packetstormsecurity.com http://packetstormsecurity.com/files/158848/SugarCRM-SQL-Injection.html referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
NVD	3.1	5.3	CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
NVD	2.0	3.5	AV:N/AC:M/Au:S/C:P/I:N/A:N

Classification

Weakness

CWE-89 Improper Neutralization of Special Elements used in an SQL Command

References

seclists.org /fulldisclosure/2020/Aug/9
exploit, mailing-list, third-party-advisory
packetstormsecurity.com /files/158848/SugarCRM-SQL-Injection.html
exploit, third-party-advisory, vdb-entry
support.sugarcrm.com /Resources/Security/sugarcrm-sa-2020-051/
release-notes, vendor-advisory

Sources

CVE List CVE-2020-17373
NVD CVE-2020-17373

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary