SQL Injection
Untrusted input is interpreted as part of a SQL query, breaking the boundary between data and code.
SQL injection occurs when user-supplied data is concatenated into a SQL statement so that the input can change the statement's structure rather than only its values.
Root cause
The core cause is mixing untrusted data with query logic instead of passing it as bound parameters.
Impact
Depending on context, impact ranges from unauthorised data disclosure to data modification and, in some environments, further compromise.
Detection methodology
Review data-access code for string-built queries; in testing, observe differential responses to benign, well-formed inputs within an authorised scope.
Remediation
Use parameterised queries / prepared statements everywhere; apply least-privilege database accounts; validate and canonicalise input; avoid dynamic SQL.
Secure coding guidance
Prefer an ORM or query builder with bound parameters. Never build SQL by string concatenation. Treat all external input as untrusted.