First published: Sun Sep 17 2017(Updated: )
An issue was discovered in SugarCRM before 7.7.2.3, 7.8.x before 7.8.2.2, and 7.9.x before 7.9.2.0 (and Sugar Community Edition 6.5.26). Several areas have been identified in the Documents and Emails module that could allow an authenticated user to perform SQL injection, as demonstrated by a backslash character at the end of a bean_id to modules/Emails/DetailView.php. An attacker could exploit these vulnerabilities by sending a crafted SQL request to the affected areas. An exploit could allow the attacker to modify the SQL database. Proper SQL escaping has been added to prevent such exploits.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
SugarCRM | <=7.7.2.2 | |
SugarCRM | =6.5.26 | |
SugarCRM | =7.8.0.0 | |
SugarCRM | =7.8.0.1 | |
SugarCRM | =7.8.1.0 | |
SugarCRM | =7.8.2.0 | |
SugarCRM | =7.8.2.1 | |
SugarCRM | =7.9.0.0 | |
SugarCRM | =7.9.0.1 | |
SugarCRM | =7.9.1.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2017-14508 is classified as a high severity vulnerability due to its potential for SQL injection attacks.
To fix CVE-2017-14508, update SugarCRM to the latest version which addresses the vulnerabilities.
CVE-2017-14508 affects SugarCRM versions prior to 7.7.2.3, 7.8.x before 7.8.2.2, 7.9.x before 7.9.2.0, and Community Edition 6.5.26.
No, CVE-2017-14508 requires authentication, meaning an attacker must be logged in to exploit this vulnerability.
CVE-2017-14508 allows an authenticated user to perform SQL injection attacks, potentially compromising the database.