PulseAugur
EN
LIVE 09:37:13

Cursor AI may expose Supabase data without RLS policies

A user on Reddit's r/cursor subreddit has highlighted a potential security vulnerability when using the Cursor AI coding assistant to set up Supabase projects. The assistant can generate code that uses Supabase's public anon key, which, without Row Level Security (RLS) policies, exposes entire tables to unauthorized access. The user emphasizes that Cursor does not proactively offer to write these crucial RLS policies, leaving developers to implement them manually to secure their data. AI

IMPACT Highlights a potential security risk in AI coding assistants when integrating with backend services, underscoring the need for developers to remain vigilant.

RANK_REASON User-reported potential security issue with an AI coding assistant.

Read on r/cursor →

AI-generated summary · Google Gemini · from 1 sources. How we write summaries →

Cursor AI may expose Supabase data without RLS policies

COVERAGE [1]

  1. r/cursor TIER_2 English(EN) · /u/UltimateScripted ·

    PSA: Cursor will happily write your Supabase queries without RLS policies

    <!-- SC_OFF --><div class="md"><p>Ran into this on a project and then found it in three others I looked at. Posting because it's silent, nothing errors, nothing warns you.</p> <p>If you ask Cursor to set up Supabase and build CRUD, you'll usually get working code using the anon k…