CVE-2017-14508: SQL Injection
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 beanid 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.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2017-14508?
CVE-2017-14508 is classified as a high severity vulnerability due to its potential for SQL injection attacks.
How do I fix CVE-2017-14508?
To fix CVE-2017-14508, update SugarCRM to the latest version which addresses the vulnerabilities.
What versions of SugarCRM are affected by CVE-2017-14508?
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.
Can CVE-2017-14508 be exploited by unauthenticated users?
No, CVE-2017-14508 requires authentication, meaning an attacker must be logged in to exploit this vulnerability.
What types of attacks are possible with CVE-2017-14508?
CVE-2017-14508 allows an authenticated user to perform SQL injection attacks, potentially compromising the database.