INJ-004critical SeverityInjection Sinks & Input Validation
No child_process.exec with Unsanitized User Input
AI scripts that invoke shell commands often concatenate user parameters into exec(`ffmpeg -i ${filename}`) enabling arbitrary command injection.
1-Click Fix Prompt for Cursor & Claude Code
Review my codebase for "No child_process.exec with Unsanitized User Input" (INJ-004).
Issue: AI scripts that invoke shell commands often concatenate user parameters into exec(`ffmpeg -i ${filename}`) enabling arbitrary command injection.
Remediation required: Use child_process.execFile or spawn with an array of arguments rather than shell string execution.
Please:
1. Locate any occurrences of this issue across my repository.
2. Refactor the code to follow production standards without breaking existing functionality.
3. Provide a clear command or step to test and verify the fix.Why AI Assistants Write This Bug
AI scripts that invoke shell commands often concatenate user parameters into exec(`ffmpeg -i ${filename}`) enabling arbitrary command injection.
AI code generation prioritizes immediate syntax execution over production edge cases. When an assistant hits an undefined variable or strict type error, it frequently takes the path of least resistance rather than implementing standard pre-launch security patterns.
Code Comparison
Common AI Code PatternVulnerable
// Vulnerable AI-generated pattern for: No child_process.exec with Unsanitized User Input
// Problematic pattern: AI scripts that invoke shell commands often concatenate user parameters into exec(`ffmpeg -i ${filename}`) enabling arbitrary command injection.Launch-Ready Fix
// Production-ready fix for: No child_process.exec with Unsanitized User Input
// Recommended remediation: Use child_process.execFile or spawn with an array of arguments rather than shell string execution.Remediation & Verification Checklist
Remediation: Use child_process.execFile or spawn with an array of arguments rather than shell string execution.
- Search your codebase for pattern matching "No child_process.exec with Unsanitized User Input".
- Apply the recommended remediation: Use child_process.execFile or spawn with an array of arguments rather than shell string execution.
- Run local build and test commands to ensure no regressions.
- Verify in your browser or with curl that the issue is resolved.
Audit All 108 Checks in One Click
Checking items one by one takes hours. Let us do it in 2 minutes.
With the Founder Pass ($15 one-time), we automatically scan your repository for this issue, plus all other 107 launch checks across secrets, Stripe webhooks, Supabase RLS, and security headers.