A vibe-coded app is usually insecure in the same few places: database tables that anyone can read or write, secret keys bundled into the browser, permission checks that only exist in the user interface, and dependencies that nobody chose on purpose. Before you launch, check those four areas first, then any feature that calls an LLM, then error handling and abuse limits. This checklist is built from the OWASP Top 10:2025, the OWASP Top 10 for LLM Applications 2025 and the Supabase, Firebase, Next.js and GitHub documentation, all read on November 16, 2026.

"Vibe coding" here means building an app mainly by prompting an AI coding tool and accepting what it produces, often without reading every line. The tools are not the problem. The problem is that a prototype prompt asks for features, and security controls are rarely features anyone can see in a demo.

Why vibe-coded apps fail in the same places

The OWASP Top 10:2025 puts broken access control first, security misconfiguration second and software supply chain failures third. Those three map closely onto what a fast, prompt-driven build leaves behind. A demo works when the only user is you, so missing access rules do not show up. A default setting that made development easy stays in place. And a coding agent can add packages faster than anyone reviews them.

That is our reading of where the risk concentrates, not an OWASP statement about AI-built apps. The practical point is that you cannot rely on the code having been reviewed, so the checks below are written as things to test in the running app.

1. Database access rules

Many vibe-coded apps talk to a hosted database straight from the browser, typically Supabase or Firebase. In that design the database's own access rules are the security boundary, and nothing else stands in front of the data.

If you use Supabase

If you use Firebase

2. Keys and secrets

Coding agents also read secrets from your machine while they work. Our post on Claude Code settings.local.json and keeping secrets out covers that side.

3. Authorization on the server

4. Dependencies an AI tool added

5. LLM features inside the app

If the app itself calls an LLM, the OWASP Top 10 for LLM Applications 2025 applies on top of the web checks. The items that matter most for a small app are:

6. Errors, logs and abuse limits

Using an AI coding agent to help check

You can ask your coding agent to go through this list against the codebase, and it will find real problems. Two cautions. First, the same agent that wrote the code may share its blind spots, so treat its review as a first pass, not a sign-off. Second, several checks above can only be confirmed against the running app: trying another user's ID, calling a table as a signed-out user, or searching the deployed bundle. Some vendors now publish agent instructions for their own security setup; Firebase's rules guide, for example, includes a prompt for AI coding agents.

What this checklist does not cover

This is a pre-launch baseline, not a full security review. It does not replace a penetration test, a threat model for sensitive data, or compliance work such as GDPR or HIPAA obligations. If the app handles payments, health data or other people's personal data at any scale, have someone review it who did not build it. If agents run with access to your machine or production systems, also see our posts on sandboxing AI agents and the AI agent security checklist.

How we approach this

When a team brings us a prototype built with AI tools, we start from the data layer and the keys, because that is where a single mistake exposes everything. Then we add server-side authorization, tests for the access rules, and limits on anything that costs money per call, before the app is opened to real users. That review is part of our web and SaaS development and AI governance and security work, and it is often the step that decides whether a prototype is ready for production; our post on why AI prototypes fail in production covers the rest of that gap.

Sources: OWASP Top 10:2025, OWASP Top 10 for LLM Applications 2025, Supabase, Row Level Security (updated November 3, 2026), Supabase, API keys, Firebase, Avoid insecure rules, Next.js, environment variables, GitHub, push protection, Spracklen et al., "We Have a Package for You!" (arXiv 2406.10279). All read on November 16, 2026.