Stored_XSS issue exists @ src/main/java/org/owasp/benchmark/testcode/BenchmarkTest01436.java in branch master
The application's doPost embeds untrusted data in the generated output with println, at line 40 of src\main\java\org\owasp\benchmark\testcode\BenchmarkTest01436.java. 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 doPost method with input, at line 40 of src\main\java\org\owasp\benchmark\testcode\BenchmarkTest01436.java. 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 @ src/main/java/org/owasp/benchmark/testcode/BenchmarkTest01436.java in branch master
The application's doPost embeds untrusted data in the generated output with println, at line 40 of src\main\java\org\owasp\benchmark\testcode\BenchmarkTest01436.java. 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 doPost method with input, at line 40 of src\main\java\org\owasp\benchmark\testcode\BenchmarkTest01436.java. 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
Lines: 67
Code (Line #67):