High severityPythonInjectionMEDIUM confidence
SQL Injection Cursor Execute
SQL query is built with string formatting/concatenation, allowing SQL injection (CWE-89).
Standards mapping
- OWASP Top 10
- A03:2021 - Injection
- OWASP ASVS
- V5.3.4 (L1)
Vulnerable vs. safe
Flagged by this check
cursor.execute("SELECT * FROM users WHERE id = " + user_id)Passes - the safe pattern
cursor.execute("SELECT * FROM users WHERE id = %s", (user_id,))Why it matters & how to fix it
SQL query is built with string formatting/concatenation, allowing SQL injection (CWE-89). Use parameterized queries: pass values as the second argument to execute() with %s / ? / named placeholders — never build the query string with %, +, .format(), or f-strings.
References
Rule ID integsec-python-sql-injection-cursor-execute - engine: Opengrep - license: MIT - Copyright (c) IntegSec Inc.
TurboPentest runs this check automatically
Connect a GitHub repo and this check runs on every white-box pentest - AI-validated and reported with proof, from $99 per target.
Start a pentestRelated checks
- JavaScript / TypeScript - InjectionCode Injection Tainted Input
- JavaScript / TypeScript - InjectionEval Dynamic Argument
- JavaScript / TypeScript - InjectionNoSQL Query From Request
- JavaScript / TypeScript - InjectionNoSQL Where Operator
- JavaScript / TypeScript - InjectionOS Command Injection Tainted Input
- JavaScript / TypeScript - InjectionSQL Injection String Concatenation