Details may change as reporting changes. Information comes from the linked sources, and we do not guarantee it is complete or current.
In plain English
Many AI app builders store your app's data in a database called Supabase. Supabase hands your app a public key that is meant to be visible in the app's code. That is normal and safe, but only if a feature called Row Level Security (RLS) is turned on and set up. RLS is the rule that says who may see or change which row.
When RLS is missing, that public key acts like a master key. Anyone who finds it can read or change everything in the table. Nothing needs to be hacked, because the door was simply unlocked.
A security researcher scanned apps built with the AI tool Lovable and reported that 170 out of 1,645 had exposed data. The issue was published as CVE-2025-48757. The point is not one tool's fault. It is that fast AI building can skip a step nobody told the builder about.
Words used here
- Database
- Where your app stores its information, like a giant spreadsheet.
- Row Level Security (RLS)
- Rules that control who can see or change each row of data.
- Public (publishable) key
- A key that is meant to be visible in an app. Supabase used to call it the anon key. It is safe only when RLS is set up.
- Secret key
- A powerful key that skips those rules. Supabase used to call it the service_role key. It must never appear in an app's public code.
What happened
The US government's flaw database entry for CVE-2025-48757 (published May 30, 2025) describes missing database access rules in Lovable, up to April 15, 2025, that let outsiders who were not signed in read or change any table of data on sites it generated.
Important: NVD notes the CVE is disputed by Lovable, which says each customer is responsible for protecting the data of their own application. Both views point to the same practical lesson: whoever builds the app has to check that the rules are on.
Secondary reporting says the researcher scanned 1,645 Lovable showcase apps and found 170 with exposed user data. Treat that count as the researcher's reported finding, not an independently confirmed one.
Reports say the exposed data included personal details and, in some apps, API keys. Details differ between sources.
How it unfolded
- May 2025
The CVE is published after the researcher's scan and disclosure.
Who was affected
Users of generated apps whose databases lacked proper rules. The exact list is not public.
What the response was
- The issue was disclosed publicly as a CVE.
- Builders were advised to review the security rules on their database tables.
What went wrong
- Apps shipped with public database access that was not protected by rules.
- Non-engineer builders did not know the missing rule existed.
What worked
- Public disclosure raised awareness of the check builders should run.
What a small team should do differently
- Turn on Row Level Security for every table and write a rule for it.
- Never put a secret (formerly service_role) key in browser code.
- Ask your AI tool to explain which tables are publicly readable, then test that yourself while logged out.
What you can do today
- Open your Supabase project > Table Editor. Any table showing RLS disabled needs a policy before real users touch it.
- Read Supabase's Row Level Security guide and follow its checklist.
- Search your app code for a key named service_role or starting with sb_secret_. If it appears in browser code, rotate it now.
Official help for the platforms involved
The lesson to take away
AI can build the app. It will not always remember to lock the door. Check who can read your data.
Sources
- NVD: CVE-2025-48757NIST National Vulnerability Database
- Supabase docs: Row Level SecuritySupabase
Finished this one?
Add it to What I learned and earn 40 Trust. You can open your list from the badge at the bottom of the page.