Why Next.js Apps Get Hacked
Next.js makes it trivially easy to blur the line between server and client. That speed is exactly why Next.js apps leak secrets and ship insecure defaults. Environment variables prefixed with NEXT_PUBLIC_ get inlined into the browser bundle, Server Actions and Route Handlers can expose internal logic, and middleware auth is easy to bypass when matchers are wrong. We scan for the failure modes that hit real Next.js deployments.
Common Next.js Vulnerabilities
Leaked NEXT_PUBLIC_ secrets
Any env var prefixed with NEXT_PUBLIC_ is baked into the client bundle. Teams routinely expose service keys, Supabase service-role keys, and third-party API tokens this way.
Server Action / SSRF exposure
Server Actions and fetch-on-server patterns can be abused for Server-Side Request Forgery — older Next.js versions had a documented SSRF (CVE-2024-34351). Keep Next.js patched and validate every server-side URL.
Middleware auth bypass
Auth enforced only in middleware with a loose matcher (or relying on a spoofable header) lets attackers reach protected routes and API handlers directly.
Missing security headers
Next.js ships no CSP, HSTS, or X-Frame-Options by default. They must be added in next.config headers() or middleware — most apps never do.
Exposed Route Handler logic
API routes under app/api with no authorization check, no rate limiting, and verbose error messages that leak stack traces and internal paths.
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 Next.js 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