Vibe coding security checklist before you launch
Short answer
Before you launch an AI-built app, confirm five things on the deployed URL, not in the chat. The client bundle contains no server secret and no sb_secret_ key. Every private Supabase table or Firebase collection has a real rule, not USING (true) or allow if true. Authorization is enforced in the handler and the database, not only in middleware or a system prompt. Next.js and React Server Components are on a patched release if you use them. The host does not serve .env, .git, or a public bucket of backups. Then run a free scan of that URL.
Last updated · Sekrd Research
- Platform-specific versions of this list: Lovable, Bolt, Cursor, v0, Replit.
- The anon or publishable key is supposed to be public. The secret key, the LLM key, and the Stripe secret key are not.
- A free scan reads the live bundle. Probes for middleware bypass, open MCP tools, GraphQL fields, public buckets, and exposed env or git files run on a deep scan.
1. Secrets in the place visitors download
- No
NEXT_PUBLIC_,VITE_,EXPO_PUBLIC_,NUXT_PUBLIC_, orPUBLIC_variable whose name is a server secret. The table is in which env vars are public. - No
sk-,sk-svcacct-,xai-,pplx-,fw_, orsb_secret_in the built files. ElevenLabs counts whenxi-api-keyis next to the value. - An
AIzakey is allowed for Maps, Firebase, and reCAPTCHA if it is restricted. It is not allowed as the key forgenerativelanguage.googleapis.com. What to do if it already shipped. .env,.env.local, and.env.productionare gitignored and not served./.git/HEADis not a git ref on the public host.
2. The database the agent created
Supabase: walk the RLS checklist. Firebase, the mistakes that still generate cleanly:
allow read, write: if trueon/{document=**}, including a test-mode ruleset that was extended instead of replaced. The longer audit is “allow if true”.allow read, write: if request.auth != nullon user data. Any account, including anonymous auth if you left it on, can read every document.- Writes that do not check
request.auth.uid == resource.data.owner(orrequest.resource.data.owneron create). - No deny-all fallback, so a collection you forgot is allowed by a recursive wildcard match.
- Storage rules copied from Firestore test mode. An open bucket is how a project fills with other people’s files and a large bill.
A passing shape, from Firebase’s rules model: match specific collections, require the caller’s uid, and end with a deny.
rules_version = '2';
service cloud.firestore {
match /databases/{database}/documents {
match /users/{userId} {
allow read, write: if request.auth != null && request.auth.uid == userId;
}
match /{document=**} {
allow read, write: if false;
}
}
}
Deploy the rules. A file named firestore.rules in the repo does nothing until Firebase has that release. Anonymous auth plus request.auth != null is still everyone.
3. Auth on the thing that returns data
- Middleware redirects are UX. The handler checks the session. Self-hosted Next.js in the CVE-2025-29927 range can skip middleware; Vercel and Netlify were not affected, and the handler check is still the one that holds.
- A system prompt is not a role system. OWASP LLM07:2025.
- Stripe and other webhooks verify the signature. The existing walkthrough is webhook signatures in generated apps.
4. Dependencies and tools
- If you ship React Server Components,
npm lsthe threereact-server-dom-*packages against CVE-2025-55182 and upgrade Next.js to the current patched line. - MCP servers on the public origin require auth before
tools/list. MCP checklist. - A hard spend limit on every model provider, and a rate limit on your route. Alerts are not a limit.
5. The URL, once
Run through the list, deploy, then run a free scan of the URL users will open. Fix what it reports, scan again. When the app has a dashboard, an MCP endpoint, GraphQL, or files in cloud storage, add a deep scan so the read-only probes run. The difference between plans is on /pricing. What the November 2026 update will and will not flag is written down in the scanner update, including the lookalikes it leaves alone.
Frequently asked questions
What should I check before launching a vibe-coded app?
Confirm the production bundle has no server secrets, private database tables have real row or document rules, authorization is enforced in the handler and the database, patched versions are installed if you use Next.js server components, and the host does not serve .env or .git. Then scan the live URL.
Are Lovable, Bolt, Cursor, v0, and Replit apps insecure by default?
The tools are not the vulnerability. The defaults they generate often stop at “it works”: a client-side API key, a permissive database policy, or auth that is only a redirect. Each of those has a specific fix. The platform guides cover the differences.
What are the most common Firebase rules mistakes in generated apps?
Test-mode allow read, write: if true left in place; allow if request.auth != null, which lets every signed-in user read every document; writes without an owner check; no deny-all fallback; and rules that were edited in the repo but never deployed. Anonymous auth makes the auth != null rule equivalent to public access.
Sources
Don't ship until you're sekrd
Run a free scan to find the vulnerabilities your AI missed.
Scan Your App Free