Multiple vulnerabilities have been discovered in vtiger CRM, which can be exploited by malicious users to disclose sensitive information and conduct SQL injection attacks and by malicious people to conduct cross-site scripting attacks and disclose sensitive information.
1) Input passed via the "default_user_name" parameter to index.php (when "module" is set to "Users" and "action" is set to "Login") is not properly sanitised in modules/Users/Login.php before being returned to the user. This can be exploited to execute arbitrary HTML and script code in a user's browser session in context of an affected site.
2) Input passed via the "service" parameter to vtigerservice.php is not properly sanitised before being returned to the user. This can be exploited to execute arbitrary HTML and script code in a user's browser session in context of an affected site.
3) Input passed via the "module_name" parameter to modules/com_vtiger_workflow/sortfieldsjson.php is not properly verified before being used to include files. This can be exploited to include arbitrary files from local resources via directory traversal attacks and URL-encoded NULL bytes.
Successful exploitation of this vulnerability requires that "magic_quotes_gpc" is disabled.
4) Input passed to the "module" parameter in phprint.php is not properly sanitised before being returned to the user. This can be exploited to execute arbitrary HTML and script code in a user's browser session in context of an affected site.
5) Input passed to the "date_closed", "closingdate_start", "closingdate_end", "leadsource", and "sales_stage" parameters in index.php (when "module" is set to "Potentials" and "action" is set to "ListView") is not properly sanitised before being returned to the user. This can be exploited to execute arbitrary HTML and script code in a user's browser session in context of an affected site.
6) Input passed to the "query" parameter in index.php (when "module" is set to "Campaigns", "action" is set to "index", and "searchtype" is set to "BasicSearch") is not properly sanitised before being returned to the user. This can be exploited to execute arbitrary HTML and script code in a user's browser session in context of an affected site.
7) Input passed to the "subtab", "view", and "viewOption" parameters in index.php (when "module" is set to "Calendar" and "action" is set to "index") is not properly sanitised before being returned to the user. This can be exploited to execute arbitrary HTML and script code in a user's browser session in context of an affected site.
The vulnerabilities #3 and #7 are confirmed in versions 5.2.1 and 5.3.0. Other versions may also be affected.
8) Input passed to the "mode" and "profile_id" parameters in index.php (when "module" is set to "Settings" and "action" is set to "profilePrivileges") is not properly sanitised before being returned to the user. This can be exploited to execute arbitrary HTML and script code in a user's browser session in context of an affected site.
9) Input passed to the "contact_id" and "parent_id" parameters in index.php (when "module" is set to "Calendar" and "action" is set to "EditView") is not properly sanitised before being returned to the user. This can be exploited to execute arbitrary HTML and script code in a user's browser session in context of an affected site.
10) Input passed to the "start" parameter in index.php (when "module" is set to "Calendar" and "action" is set to "ListView") is not properly sanitised before being returned to the user. This can be exploited to execute arbitrary HTML and script code in a user's browser session in context of an affected site.
11) Input passed to the "viewname" parameter in index.php (when "module" is set to "Calendar" and "action" is set to "CalendarAjax") is not properly sanitised before being returned to the user. This can be exploited to execute arbitrary HTML and script code in a user's browser session in context of an affected site.
12) Input passed to the "return_url" and "workflow_id" parameters in index.php (when "module" is set to "com_vtiger_workflow" and "action" is set to "editworkflow") is not properly sanitised before being returned to the user. This can be exploited to execute arbitrary HTML and script code in a user's browser session in context of an affected site.
13) Input passed to the "activity_mode" parameter in index.php (when "module" is set to "Calendar", "action" is set to "DetailView", and "record" is set to a valid record) is not properly sanitised before being returned to the user. This can be exploited to execute arbitrary HTML and script code in a user's browser session in context of an affected site.
14) Input passed to the "display_view" parameter in index.php (when "module" is set to "Dashboard" and "action" is set to "index") is not properly sanitised before being returned to the user. This can be exploited to execute arbitrary HTML and script code in a user's browser session in context of an affected site.
15) Input passed to the "fo... (truncated text)
