security-review-owasp-injection-prevention

Review injection prevention risks across code, configuration, and architecture.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/sjinks/ai-owasp-skillset --skill security-review-owasp-injection-prevention
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-review-owasp-injection-prevention
Source: https://github.com/sjinks/ai-owasp-skillset/tree/main/.github/skills/security-review-owasp-injection-prevention
Command: npx skills add https://github.com/sjinks/ai-owasp-skillset --skill security-review-owasp-injection-prevention

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps reviewers find injection flaws where attacker-controlled input reaches interpreters, binders, redirect targets, or privileged state changes without strict control.

Core Features & Use Cases

  • Boundary Review: Traces untrusted data through validation, normalization, binding, serialization, and execution paths.
  • Exploitability Focus: Prioritizes direct code execution, query manipulation, privilege mutation, and attacker-controlled routing over superficial formatting issues.
  • Evidence-Based Reporting: Produces confirmed findings, review gaps, passed checks, and an overall assessment tied to OWASP Injection Prevention guidance.

Quick Start

Use the security-review-owasp-injection-prevention skill to review the specified flow or files for untrusted input reaching dangerous sinks and report only evidence-backed findings.

Frequently Asked Questions about security-review-owasp-injection-prevention

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

FAQPage Schema
How do I review untrusted input paths for OWASP injection prevention risks?

To review untrusted input for OWASP injection prevention risks, trace attacker-controlled data across validation, normalization, binding, serialization, and execution paths to identify where it reaches dangerous interpreters or privileged state mutations without strict control.

What is an injection prevention security review?

An injection prevention security review analyzes code, configuration, architecture, and operational controls to find flaws where attacker-controlled input reaches interpreters, binders, redirect targets, or privileged state changes without strict validation.

How do I prioritize injection vulnerabilities during a code review?

Prioritize injection vulnerabilities during code review by focusing on exploitability, ranking direct code execution, query manipulation, privilege mutation, and attacker-controlled routing higher than superficial formatting issues.

How should I report injection prevention findings?

Report injection prevention findings as severity-ordered, evidence-backed results that include confirmed flaws, review gaps, passed checks, and a final assessment aligned directly to OWASP Injection Prevention guidance.

Does this injection review cover configuration and architecture or just code?

This injection review covers configuration and architecture in addition to code, evaluating untrusted input crossing into selectors, binders, redirect targets, serialization paths, and privileged state mutations across the entire system.