Hand-written summaryWorldwide
What happened
A researcher reported that apps generated with Lovable often shipped with the database protection switch off, so anyone with the public key could read or change data. Lovable disputes the CVE, saying app owners are responsible for their data.
Rated high: action is recommended for affected people. Why: private data in many apps could be read by anyone; the tool's maker disputes who is responsible.
This incident may still be developing. Details can change.
Does this affect me?
Only if you built or use an app made with an AI app builder that stores data in Supabase.
Who may be affected: Users of apps generated with Lovable whose databases lacked proper access rules.
You may be affected if
- You use Lovable
- You shared personal details, photos or location with it
You are probably not affected if
- You do not use Lovable
- You have limited what it can see
If you are unsure: Review the privacy settings and remove permissions you do not need.
What to do now
- If you built an app with Lovable and Supabase, open Supabase and check that Row Level Security is on for every table.
- Make sure no secret (service role) key appears in your app's public code.
- Test your app as a stranger: log out and see what data you can reach.
What to do next (24 to 48 hours)
- Check what personal details the service holds about you.
- Consider whether you still need the account.
How to avoid this in future
- Share only the details a service really needs.
- Review app permissions regularly.
- Turn on two-factor authentication, ideally with an app or passkey.
What we know, and what we do not
Stated by the source
- NVD records CVE-2025-48757 as an insufficient database Row-Level Security policy in Lovable, through 2025-04-15, allowing unauthenticated users to read or write to tables of generated sites.
- NVD notes that Lovable disputes the CVE because each customer is responsible for protecting the data of their application.
Reported or claimed, not confirmed
- Secondary reporting says a researcher found 170 of 1,645 Lovable apps with exposed data. This count is not independently confirmed.
Still unclear
- How many apps were exposed and what data they held is not independently confirmed.
Entry in the national vulnerability database. The supplier disputes it.
Why it is on the radar
Worth learning from: 73/100
High relevance because it concerns accounts, money or personal information, it involves AI tools and it matters to small teams and builders.
This is our own score for how useful an item is to everyday people and small teams. It is not an objective measure of how dangerous something is.
Words used here
- CVE
- A public ID number for one known security flaw.
Sources
- NIST National Vulnerability Database: read the originalPublished 30 May 2025. Last retrieved 12 Nov 2026.
Learn more on CyberSafety.lol
Finished this one?
Add it to What I learned and earn 15 Trust. You can open your list from the badge at the bottom of the page.
This news feed monitors public reporting and official advisories. It does not capture every cyberattack worldwide.
Back to the security news feed