FREE SCAN — 150 founder credits, no card

Free Security Scan for Laravel Apps

Scan your Laravel app for .env exposure, debug leaks, and mass assignment.

Why Laravel Apps Get Hacked

Laravel ships secure defaults, but the recurring real-world incidents come from configuration: a publicly readable .env file, APP_DEBUG left on (which the Ignition error page can turn into RCE — see CVE-2021-3129), and mass assignment through unguarded models. A leaked APP_KEY breaks session and encryption integrity. We scan for the Laravel patterns attackers look for first.

Common Laravel Vulnerabilities

Exposed .env file

A misconfigured web root that serves /.env hands over database credentials, APP_KEY, mail and third-party keys in one request. A perennial Laravel breach source.

APP_DEBUG = true (Ignition RCE)

Debug mode exposes detailed errors and config; combined with a vulnerable Ignition version it enabled remote code execution (CVE-2021-3129). Disable debug in production and patch.

Mass assignment

Models without $fillable / $guarded let attackers set arbitrary columns (e.g. is_admin) via Model::create($request->all()).

Leaked APP_KEY

APP_KEY signs sessions and encrypts data. A leaked key allows session forgery and decryption of protected values.

Missing headers & rate limits

Security headers and throttling are configurable but not automatic; without them the app is exposed to clickjacking, XSS, and brute force.

What the Sable Scan Checks

Exposed secrets & API keys

We scan your client-side bundles and responses for leaked API keys, tokens, database URLs, and 100+ secret patterns that ship to the browser by accident.

Security headers & TLS

HSTS, CSP, X-Frame-Options, Referrer-Policy, Permissions-Policy, and TLS protocol/cipher configuration — graded A-F with copy-paste fixes.

CORS & access control

Overly permissive CORS, wildcard origins with credentials, and broken object-level authorization (IDOR/BOLA) where one user can reach another user's data.

Injection & API surface

SQL/NoSQL injection, exposed OpenAPI/Swagger specs, GraphQL introspection, mass assignment, missing rate limits, and excessive data exposure.

OWASP Top 10 coverage

Autonomous pentesting agents test against the full OWASP Top 10 2025, validate each finding with a proof-of-concept, and re-test after you fix.

Validated findings, not noise

Every reported issue is confirmed by an agent before it reaches you — so you get real, exploitable findings with severity and remediation, not scanner spam.

Scan Your Laravel App in Minutes

Create a free account, point the agents at your app, and get validated findings with proof-of-concept and fix guidance. 150 founder credits, no credit card.

Get 150 Free Credits

Frequently Asked Questions

How does a Laravel .env file get exposed?
Usually a misconfigured document root or web server that serves files outside /public, so /.env becomes directly fetchable — leaking DB credentials, APP_KEY, and API keys. Ensure only /public is web-accessible. Sable scans for exposed .env and config files.
Is APP_DEBUG dangerous in Laravel production?
Yes. APP_DEBUG=true exposes detailed error pages with config and environment data, and with a vulnerable Ignition version it allowed remote code execution (CVE-2021-3129). Set APP_DEBUG=false and keep dependencies patched. Sable detects debug-mode leakage.
Is the security scan really free?
Yes. The Headers Scan runs instantly with no signup. For the full agent scan you create a free account and get 150 founder credits with no credit card required — enough to run real scans against your app on demand. Paid credit packs and monthly tiers exist for continuous testing, but you can start for free.
How does Sable scan my app?
Sable runs autonomous pentesting agents (pen-scout, pen-recon, pen-triage, pen-fixer, pen-compliance) that map your attack surface, test against the OWASP Top 10, validate every finding with a proof-of-concept, and re-test after you ship a fix. You chat with the agents on demand instead of waiting weeks for a manual engagement.
Will the scan break or slow down my production app?
No. Scans are designed to be safe and non-destructive. We demonstrate impact with proof-of-concept evidence rather than causing damage, and we never exfiltrate or alter your data.

Security Scans for Other Stacks