Stored_XSS issue exists @ root/login.jsp in branch master
*The application's <td><%=username%></td> embeds untrusted data in the generated output with username, at line 57 of root\password.jsp. This untrusted data is embedded straight into the output without proper sanitization or encoding, enabling an attacker to inject malicious code into the output.The attacker would be able to alter the returned web page by saving malicious data in a data-store ahead of time. The attacker's modified data is then read from the database by the stmt.executeQuery method with rs, at line 15 of root\login.jsp. This untrusted data then flows through the code straight to the output web page, without sanitization. This can enable a Stored Cross-Site Scripting (XSS) attack.
The application's value=""/> embeds untrusted data in the generated output with username, at line 89 of root\contact.jsp. This untrusted data is embedded straight into the output without proper sanitization or encoding, enabling an attacker to inject malicious code into the output.The attacker would be able to alter the returned web page by saving malicious data in a data-store ahead of time. The attacker's modified data is then read from the database by the stmt.executeQuery method with rs, at line 15 of root\login.jsp. This untrusted data then flows through the code straight to the output web page, without sanitization. This can enable a Stored Cross-Site Scripting (XSS) attack.*
Stored_XSS issue exists @ root/login.jsp in branch master
*The application's <td><%=username%></td> embeds untrusted data in the generated output with username, at line 57 of root\password.jsp. This untrusted data is embedded straight into the output without proper sanitization or encoding, enabling an attacker to inject malicious code into the output.The attacker would be able to alter the returned web page by saving malicious data in a data-store ahead of time. The attacker's modified data is then read from the database by the stmt.executeQuery method with rs, at line 15 of root\login.jsp. This untrusted data then flows through the code straight to the output web page, without sanitization. This can enable a Stored Cross-Site Scripting (XSS) attack.
The application's value=""/> embeds untrusted data in the generated output with username, at line 89 of root\contact.jsp. This untrusted data is embedded straight into the output without proper sanitization or encoding, enabling an attacker to inject malicious code into the output.The attacker would be able to alter the returned web page by saving malicious data in a data-store ahead of time. The attacker's modified data is then read from the database by the stmt.executeQuery method with rs, at line 15 of root\login.jsp. This untrusted data then flows through the code straight to the output web page, without sanitization. This can enable a Stored Cross-Site Scripting (XSS) attack.*
Severity: High
CWE:79
Checkmarx
Training Recommended Fix
Lines: 15
Code (Line #15):