AUTH-004critical SeverityBroken Authentication & Access Controls
Row Level Security (RLS) Enabled on Supabase / PostgreSQL Tables
Lovable and Bolt create database tables via migrations but frequently forget to execute ALTER TABLE ... ENABLE ROW LEVEL SECURITY.
1-Click Fix Prompt for Cursor & Claude Code
Review my codebase for "Row Level Security (RLS) Enabled on Supabase / PostgreSQL Tables" (AUTH-004). Issue: Lovable and Bolt create database tables via migrations but frequently forget to execute ALTER TABLE ... ENABLE ROW LEVEL SECURITY. Remediation required: Verify every table in your public database schema has RLS active and explicit SELECT, INSERT, UPDATE, DELETE policies defined. Please: 1. Locate any occurrences of this issue across my repository. 2. Refactor the code to follow production standards without breaking existing functionality. 3. Provide a clear command or step to test and verify the fix.
Why AI Assistants Write This Bug
Lovable and Bolt create database tables via migrations but frequently forget to execute ALTER TABLE ... ENABLE ROW LEVEL SECURITY.
AI code generation prioritizes immediate syntax execution over production edge cases. When an assistant hits an undefined variable or strict type error, it frequently takes the path of least resistance rather than implementing standard pre-launch security patterns.
Code Comparison
Common AI Code PatternVulnerable
// Vulnerable AI-generated pattern for: Row Level Security (RLS) Enabled on Supabase / PostgreSQL Tables
// Insecure route handler trusting body user ID (IDOR risk)
export async function POST(req: Request) {
const { userId, newEmail } = await req.json();
// BUG: Any user can modify any other user record!
await db.user.update({ where: { id: userId }, data: { email: newEmail } });
return Response.json({ success: true });
}Launch-Ready Fix
// Production-ready fix for: Row Level Security (RLS) Enabled on Supabase / PostgreSQL Tables
// Protected route deriving identity from verified session
export async function POST(req: Request) {
const session = await auth();
if (!session?.user?.id) {
return Response.json({ error: "Unauthorized" }, { status: 401 });
}
const { newEmail } = await req.json();
// Scoped strictly to authenticated session user ID
await db.user.update({ where: { id: session.user.id }, data: { email: newEmail } });
return Response.json({ success: true });
}Remediation & Verification Checklist
Remediation: Verify every table in your public database schema has RLS active and explicit SELECT, INSERT, UPDATE, DELETE policies defined.
- Search your codebase for pattern matching "Row Level Security (RLS) Enabled on Supabase / PostgreSQL Tables".
- Apply the recommended remediation: Verify every table in your public database schema has RLS active and explicit SELECT, INSERT, UPDATE, DELETE policies defined.
- Run local build and test commands to ensure no regressions.
- Verify in your browser or with curl that the issue is resolved.
Audit All 108 Checks in One Click
Checking items one by one takes hours. Let us do it in 2 minutes.
With the Founder Pass ($15 one-time), we automatically scan your repository for this issue, plus all other 107 launch checks across secrets, Stripe webhooks, Supabase RLS, and security headers.