01Description
User-supplied input was incorporated into a database query without parameterization, allowing an attacker to alter the structure of the query.
02Impact
An attacker can read data from the database beyond their authorization, including other users' records and credentials, and depending on configuration may modify data or execute commands on the database server.
03Severity
Typically
Critical
Typically Critical. Usually Critical or High. Severity depends on the data reachable and whether the injection allows writing data or executing commands.
04How to verify
- 1Identify inputs that reach database queries.
- 2Confirm injection with safe techniques such as boolean or time-based tests, avoiding destructive payloads.
- 3Where authorized, demonstrate impact by retrieving the database version or a non-sensitive record only.
Testing note: only test systems you are authorized to test, within the agreed scope and rules of engagement. Verification steps are written for professional testers and avoid destructive techniques.
05Remediation
- 1Use parameterized queries or prepared statements for every database call.
- 2Use an ORM safely and avoid building queries with string concatenation.
- 3Apply least privilege to the application's database account.
- 4Validate input types as defense in depth.
06References
Draft findings like this from your own evidence
Book a demo