php-auth-audit

To identify authentication and authorization mechanisms in a PHP web application, you can use source-level static analysis to detect Session, JWT, middleware, or custom validation functions and map their enforcement across routes.

The best way to audit PHP routes for IDOR and authorization bypass risks is by generating a route-auth mapping that assesses each route's authentication state and flags potential vertical or horizontal privilege escalation vulnerabilities.

Yes, you can audit PHP authentication flows without runtime traces by using the STATIC_MAPPING mode, which performs source-level analysis to identify authorization mechanisms and map route protection statuses statically.

Source-level code audit detects broken access control in PHP projects by analyzing authentication chains and evaluating route-level authorization states to uncover missing checks, bypass paths, and IDOR vulnerabilities.

No, you do not need runtime traces to generate a route-auth mapping for PHP applications; the analysis supports a STATIC_MAPPING mode that works purely from source code to identify authentication states and risks.

A key limitation of using static mapping for PHP authorization audits is the absence of runtime execution context, meaning dynamic includes or runtime-evaluated middleware conditions may not fully resolve without switching to TRACE_AUDIT mode.