Directory Traversal
User input is not used directly in filesystem paths.
- Severity
- Critical
- Typical fix
- ~10 minutes
- Analyzer
- DirectoryTraversalAnalyzer
What it checks
A focused signal for security risk.
User input is not used directly in filesystem paths. LaraBeacon evaluates the relevant Laravel code, configuration, dependency, or runtime boundary and reports the concrete location whenever the analyzer can identify one.
Recommended response
Fix the cause, then lock in the decision.
Treat the finding as a security boundary: remove untrusted input from the sensitive operation and add a regression test for the protected path.
If the behavior is intentional, document the decision through LaraBeacon’s baseline or analyzer configuration instead of silently ignoring the result in a release pipeline.
Availability
Included in LaraBeacon Pro.
This analyzer is part of the private Pro package. Pro builds on the public engine while keeping its deeper analyzers in a separate package.