sql-injection

Identify SQL injection vulnerabilities in source code via taint analysis.

7|1|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/ArianHobson333/claude-bug-bounty-stack --skill sql-injection-arianhobson333
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sql-injection
Source: https://github.com/ArianHobson333/claude-bug-bounty-stack/tree/main/vendor/Decepticon/skills/analyst/sql-injection
Command: npx skills add https://github.com/ArianHobson333/claude-bug-bounty-stack --skill sql-injection-arianhobson333

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill identifies SQL injection vulnerabilities by tracing the flow of untrusted input through a codebase, alerting developers to potential security risks.

Core Features & Use Cases

  • Source-level Taint Tracking: Analyzes code at the source to find points where user input may be used insecurely.
  • Language-Specific Analysis: Detects SQL injection flaws in various programming languages and frameworks.
  • Use Case: It can be integrated into a development pipeline to automatically scan applications for SQL injection flaws during the development or testing phase.

Quick Start

Run 'semgrep --config p/sql-injection /workspace/src --sarif -o /workspace/sem-sqli.sarif' to analyze your source code for SQL injection vulnerabilities.

Frequently Asked Questions about sql-injection

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How does taint analysis detect SQL injection vulnerabilities in source code?

Source-level taint analysis detects SQL injection by tracing the flow of untrusted user input through a codebase to find points where it is insecurely applied to SQL queries, reducing the risk of injection attacks.

How do I scan my application for SQL injection flaws during development?

You can scan for SQL injection flaws by running a source-code analysis tool like semgrep against your workspace directory. This identifies potential vulnerabilities by tracking insecure user input application to SQL queries.

Does this SQL injection detection work across different programming languages and frameworks?

Yes, the SQL injection detection performs language-specific analysis to identify vulnerabilities across various programming languages and frameworks. It traces untrusted input flow to secure SQL query application regardless of the stack.

What is the best way to integrate SQL injection vulnerability detection into a development pipeline?

The best way to integrate SQL injection detection is to run source-code analysis automatically during the development or testing phase. This scans applications for vulnerabilities by tracing untrusted input flow to SQL queries.

Why do I need source-level analysis to find SQL injection vulnerabilities instead of just testing inputs?

Source-level analysis is needed to find SQL injection vulnerabilities because it performs taint tracking to trace the exact flow of untrusted input through the codebase, identifying insecure SQL query application points that dynamic testing might miss.