SQL Injection attacks are primarily a problem for web applications using a relational database to store the data from users of the applications (which is how most web apps work in practice).
The developers that don't know any better treat SQL commands as text in their code, and then allow user input to be "injected" by concatenating it into the SQL command text. This allows user input to alter the SQL commands themselves, which is a horribly bad idea.
The solution is for the SQL syntax to be parameterized, which does not allow user input to change the SQL syntax no matter what. That solution has been around for DECADES now... which apparently is unknown to whoever designed and built Gab.
SQL Injection attacks are primarily a problem for web applications using a relational database to store the data from users of the applications (which is how most web apps work in practice).
The developers that don't know any better treat SQL commands as text in their code, and then allow user input to be "injected" by concatenating it into the SQL command text. This allows user input to alter the SQL commands themselves, which is a horribly bad idea.
The solution is for the SQL syntax to be parameterized, which does not allow user input to change the SQL syntax no matter what. That solution has been around for DECADES now... which apparently is unknown to whoever designed and built Gab.