Laravel security scanner: debug leaks and exposed files
Laravel is secure by default, and almost every real-world hole comes from deployment: APP_DEBUG left on, a web server pointed at the project root instead of public/, a dev package that went to production. ScanAnt looks for exactly those leftovers on your live site and, with your source, for unsafe routes in the code.
Free, no signup. We only read what your site already shows every visitor.
What we check
Each item is tagged with the scan that reports it. The quick scan is free and needs no signup. The others run only on sites you have proved you own.
Public .env file
Verified scanWhether the environment file is downloadable. It holds APP_KEY, database and mail credentials.
Debug mode
Deep scanWhether the server runs in debug mode and shows stack traces and settings when something fails.
Laravel Debugbar
Deep scanThe Debugbar request history, which can expose queries, sessions and headers of other users.
Logs and log viewers
Deep scanToday's laravel.log under storage and public log viewer pages.
Horizon
Deep scanWhether the Horizon queue API answers without the auth gate.
Composer files
Deep scancomposer.lock and vendor/composer/installed.json, which reveal the exact version of every PHP package.
Headers, cookies and TLS
Quick scanPassive checks for HSTS, CSP, framing, nosniff and session cookie flags on the public page.
Routes and PHP patterns
Code scanIn an uploaded project: endpoints with no authentication, missing owner checks, SQL built from strings, unsigned webhooks, disabled CSRF protection and requests that reach a shell command or file path.
- Verified scan: After you prove you own the site. Read-only.
- Deep scan: After you prove ownership and tick the deep option.
- Quick scan: No signup. Reads only what every visitor receives.
- Code scan: You upload your project as a ZIP.
No scan can promise to find every problem. A clean result means no known problems were found on what the scan could see.
Common mistakes
APP_DEBUG=true in production
Error pages print environment values and the stack, which can include credentials.
Document root set to the project folder
.env, storage and vendor become downloadable instead of only public/.
Leaving Debugbar or Telescope installed in production
They record requests, queries and headers that are meant for developers only.
Horizon or log viewers without a gate
Anyone can read job payloads and logs, and sometimes retry or delete jobs.
Routes that skip the auth middleware
A forgotten middleware group turns an internal action into a public one.
How to fix it
Set APP_DEBUG=false and DEBUGBAR_ENABLED=false on production, then clear and rebuild the config cache.
Point the web server at the public/ directory only, and deny dotfiles and storage in its config.
Install dev tools as require-dev and deploy with composer install --no-dev.
Protect Horizon and any log viewer with their authorization gate, and run them behind your admin login.
Rotate APP_KEY and credentials if a .env file or log was ever publicly reachable.
Questions
Which Laravel versions are supported?
The scans look at behaviour and files, not at a version list. The code scan reads PHP projects in general, so it works for older and newer Laravel releases alike.
What happens if I rotate APP_KEY?
Encrypted cookies and sessions are invalidated and encrypted database fields cannot be decrypted with the new key. Plan the rotation, but do it if the key was exposed.
Does the scan hit my admin panel or Nova?
It checks whether admin-looking and tooling paths such as Horizon respond without a login. It never logs in and never submits a form.
Is the passive scan enough for Laravel?
It covers headers, cookies and front-end code. The leaks that matter most for Laravel, like .env and debug pages, come from the verified scan after ownership proof.
Related checks
A free website vulnerability scanner that explains every finding
Known CVEs, injection probes, open redirects and exposed files, in plain language.
Open →WordPress security scanner for live sites
Backups, user lists, XML-RPC, outdated plugins and debug leftovers on WordPress.
Open →Security headers check: CSP, HSTS and friends
Is your CSP, HSTS, framing and referrer policy set up properly?
Open →
Run the scan now
Free for any public site, no signup. Need the verified, deep or code scan? Choose the level on the scan page.
Choose a scan level →