php-cmd-audit

To detect PHP command injection vulnerabilities, trace user input data flow paths to command execution sinks like exec, system, and shell_exec. This analysis enforces an end-to-end evidence chain per sink to validate exploitability and provides remediation guidance.

Static analysis traces user input to command execution sinks by mapping end-to-end data-flow paths from input sources to system calls. It enforces a data-flow evidence chain per sink to verify if unfiltered user input reaches command construction points.

Yes, you can apply static analysis for PHP security audits before deployment. It validates suspected command injection points by tracing data flow from inputs to system calls, outputting reproducible PoC templates and fix recommendations for regression verification.

The best way to find unfiltered user input in PHP system calls is applying end-to-end data-flow tracing. This validates exploitability by enforcing a data-flow evidence chain per sink and checking the Sink Evidence Type Checklist against route tracing outputs.

False positives for command injection often occur when analysis lacks end-to-end data-flow evidence. Enforcing a data-flow evidence chain per sink and requiring PoC templates ensures only exploitable paths where unfiltered input enters system calls are reported.

Yes, you need route tracing outputs to effectively audit PHP command injection risks. The analysis relies on php-route-tracer outputs to map input sources and validate the end-to-end data-flow chain leading to command execution sinks.