SQL_Injection issue exists @ server/server.js in branch main
*The application's app.patch method executes an SQL query with CxAssociativeArray_95b444c4, at line 48 of server\server.js. The application constructs this SQL query by embedding an untrusted string into the query without proper sanitization. The concatenated string is submitted to the database, where it is parsed and executed accordingly.
An attacker would be able to inject arbitrary syntax and data into the SQL query, by crafting a malicious payload and providing it via the input complete; this input is then read by the app.patch method at line 49 of server\server.js. This input then flows through the code, into a query and to the database server - without sanitization.
This may enable an SQL Injection attack.
The application's app.delete method executes an SQL query with id, at line 42 of server\server.js. The application constructs this SQL query by embedding an untrusted string into the query without proper sanitization. The concatenated string is submitted to the database, where it is parsed and executed accordingly.
An attacker would be able to inject arbitrary syntax and data into the SQL query, by crafting a malicious payload and providing it via the input id; this input is then read by the app.delete method at line 42 of server\server.js. This input then flows through the code, into a query and to the database server - without sanitization.
This may enable an SQL Injection attack.
The application's app.patch method executes an SQL query with id, at line 48 of server\server.js. The application constructs this SQL query by embedding an untrusted string into the query without proper sanitization. The concatenated string is submitted to the database, where it is parsed and executed accordingly.
An attacker would be able to inject arbitrary syntax and data into the SQL query, by crafting a malicious payload and providing it via the input id; this input is then read by the app.patch method at line 48 of server\server.js. This input then flows through the code, into a query and to the database server - without sanitization.
This may enable an SQL Injection attack.
*
SQL_Injection issue exists @ server/server.js in branch main
*The application's app.patch method executes an SQL query with CxAssociativeArray_95b444c4, at line 48 of server\server.js. The application constructs this SQL query by embedding an untrusted string into the query without proper sanitization. The concatenated string is submitted to the database, where it is parsed and executed accordingly. An attacker would be able to inject arbitrary syntax and data into the SQL query, by crafting a malicious payload and providing it via the input complete; this input is then read by the app.patch method at line 49 of server\server.js. This input then flows through the code, into a query and to the database server - without sanitization. This may enable an SQL Injection attack.
The application's app.delete method executes an SQL query with id, at line 42 of server\server.js. The application constructs this SQL query by embedding an untrusted string into the query without proper sanitization. The concatenated string is submitted to the database, where it is parsed and executed accordingly. An attacker would be able to inject arbitrary syntax and data into the SQL query, by crafting a malicious payload and providing it via the input id; this input is then read by the app.delete method at line 42 of server\server.js. This input then flows through the code, into a query and to the database server - without sanitization. This may enable an SQL Injection attack.
The application's app.patch method executes an SQL query with id, at line 48 of server\server.js. The application constructs this SQL query by embedding an untrusted string into the query without proper sanitization. The concatenated string is submitted to the database, where it is parsed and executed accordingly. An attacker would be able to inject arbitrary syntax and data into the SQL query, by crafting a malicious payload and providing it via the input id; this input is then read by the app.patch method at line 48 of server\server.js. This input then flows through the code, into a query and to the database server - without sanitization. This may enable an SQL Injection attack. *
Severity: High
CWE:89
Checkmarx
Training Recommended Fix
Lines: 48 49 42
Code (Line #48):
Code (Line #49):
Code (Line #42):