- Home
- Skills
- Data & Databases
- SQL Injection Risk Assessment Engineer
Works with the AI Agents you already use
SQL Injection Risk Assessment Engineer
A specialized security engineer for auditing SQL injection risk in code, ORMs, and database configurations.
$29.99
SQL Injection Risk Assessment Engineer
Example session with this skill installed
Review this Node.js repository snippet for SQL injection risk. We use pg-promise but have some raw queries for a search feature. The search term comes from a GET parameter.
- Read your context and instructions
- Compiled the sql injection risk
I have reviewed the provided Node.js code snippet utilizing pg-promise. The assessment identified one confirmed unsafe query pattern involving dynamic string interpolation for a search feature.
SQL Injection Risk Assessment Report
Assessment metadata
- Application: Internal Search API
- Language/Framework: Node.js / Express
- Database: PostgreSQL (pg-promise)
- Review Type: Static Code Review
- Evidence Sources:
search.controller.js,db.js
Findings Summary
| ID | Finding | Severity | Confidence | Affected Component | Status |
|---|---|---|---|---|---|
| SQLI-01 | String Interpolation in Raw Query | Critical | High | GET /api/v1/search | Confirmed Unsafe |
| SQLI-02 | Unsafe Sort Identifier | Medium | Medium | QueryBuilder.ts | Potential Risk |
Detailed Finding: SQLI-01
- Severity: Critical | Confidence: High
- Location:
search.controller.jsline 42 - Evidence:
const results = await db.query("SELECT * FROM items WHERE name LIKE '%" + req.query.term + "%'");
Data-Flow: The term parameter is taken directly from the URL query string and concatenated into the SQL statement without sanitization or parameter binding.
Impact: An attacker can terminate the string and execute arbitrary SQL commands, potentially leading to unauthorized data extraction or table deletion.
Remediation: Use pg-promise variable injection syntax ($1) to ensure the value is handled as a bound parameter.
Secure Coding Guidance (Node.js/pg-promise)
// SECURE: Using bound parameters
const searchTerm = `%${req.query.term}%`;
const results = await db.query('SELECT * FROM items WHERE name LIKE $1', [searchTerm]);
Next steps
- Replace string concatenation in
search.controller.jswith the parameterized query provided above. - Review
QueryBuilder.tsto ensure column names in theORDER BYclause are checked against a strict allowlist. - Run the suggested regression test in the staging environment using synthetic data.
Connects securely to your tools. The creator never sees your data.
About this skill
Manually auditing source code for SQL injection is slow and prone to oversight. This skill acts as a dedicated risk assessment engineer to identify unsafe query patterns, trace untrusted data flows, and provide structured remediation guidance for authorized security reviews.
What it does
- Static code analysis reviews source files to detect string concatenation, unsafe interpolation, and raw SQL escape hatches in ORMs.
- Data flow tracing follows user-controlled input from HTTP headers, bodies, and parameters down to the database execution boundary.
- Risk classification assigns severity and confidence scores to findings based on reachability, database privileges, and potential impact.
- Remediation engineering generates language-specific secure coding examples using prepared statements and bound parameters.
- Verification planning designs safe regression tests and synthetic data fixtures to validate fixes without risking production environments.
How it works
- Scope Definition: Provide the application name, tech stack, and authorized review boundaries to establish the assessment context.
- Evidence Review: Supply source code, ORM models, query logs, or sanitized configuration files for analysis.
- Path Inventory: The agent maps entry points to database operations, flagging unreviewed or suspicious code paths.
- Report Generation: Receive a structured SQL injection risk assessment including an executive summary, findings table, and prioritized roadmap.
Frameworks & tools
Works with any SQL-based architecture including PostgreSQL, MySQL, SQL Server, and Oracle. Supports review of ORM implementations like Sequelize, TypeORM, SQLAlchemy, and Eloquent, as well as raw database drivers.
Why this beats prompting it yourself
Generic prompts often miss the nuance between data values and identifiers or fail to account for least-privilege database roles. This skill uses a systematic workflow to ensure no secondary query paths or ORM escape hatches are overlooked during the audit.
Use cases
- Reviewing legacy codebases for concatenation-based SQL injection before a major migration.
- Auditing raw SQL queries and dynamic filters in reporting tools or internal dashboards.
- Generating secure coding patterns for developers after a vulnerability is detected in a PR.
- Validating that ORM usage consistently applies parameterization across all API routes.
Known limitations
Does not perform live exploitation, database scanning, or automated code patching. Quality depends entirely on the completeness of supplied source code and sanitized logs.
Requires manual provision of source code or logs. Assessment is limited to provided evidence. No live scanning or automated patching.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 10 days ago