Lovable security review
Lovable security: what the scanner catches, and what it cannot
Lovable checks your app every time you publish. The questions it cannot answer are the ones that decide whether you can safely take money.
You built your app in Lovable, people are using it, and now you have read about CVE-2025-48757, or Lovable's security view is showing warnings you are not sure how to judge. You want to know whether customers can see each other's data, whether your keys are safe, and whether the payment flow can be fooled. That is what our vibe coded app audit answers; this page covers the Lovable security issues we look at in particular.
Whether your project uses Lovable Cloud or your own Supabase project, the data sits in Supabase: every Lovable Cloud project runs on Supabase. So the same rules decide who sees what, and the same mistakes leave data open.
4 findings, a fix for each
Ranked by what an attacker could do with them
- CriticalRow-level security is off on 3 tablesDatabase: orders, invoices, profilesFix included
- HighService key shipped to the browserFrontend bundle: supabase.tsFix included
- HighAdmin role checked in the client onlyRoute: /admin/usersFix included
- MediumNo rate limit on sign-inAuth: password sign-inFix included
About to take payments or personal data through a Lovable app?
We review the policies, functions, keys and payment flow behind it and send you a ranked list of what to fix first.
What Lovable checks for you
Lovable's security features are genuinely useful. A quick scan runs every time you publish and reviews the database for tables without row-level security, rules that allow everyone and leaked-password protection being off, along with known-vulnerable packages. A Deep scan, which you start yourself, reads the code for access-control gaps, unauthenticated endpoints, injection, leaked secrets, payment and billing problems, weak account security and exposed personal data. Business and Enterprise workspaces also get a security centre, Enterprise adds scheduled scans, and a workspace setting can block publishing while critical issues are open.
Lovable is also honest about the limits. Its documentation says you are responsible for making sure your app meets the security requirements of its use case, that the tools cannot guarantee complete security, and it recommends a professional security review for apps that handle sensitive data or critical functions. What no scan can tell you:
- Whether the rules match your business. A scan can see that a policy exists, not whether a manager should be able to see another team's data.
- Whether payments are safe end to end, including refunds, upgrades, cancellations and webhooks that arrive twice.
- Whether one company's data stays apart from another's in a product you sell to businesses.
- Whether an automatic fix broke sign-up, a webhook or an integration somewhere else.
- Anything that changed after the last Deep scan, since it only runs when someone starts it.
The Lovable security issues we check first
- 1
Row-level security that is on, but lets too much through
Lovable's scan flags tables with no row-level security and rules that allow everyone. What it cannot know is whether a policy matches your business: a team member who can see other teams' records, a customer who can update an order after it has shipped, or an admin check that compares the wrong column. When policies look right but data still leaks, or the app breaks after you tighten them, the causes are usually the ones in why Supabase RLS is not working.
- 2
Roles and plans that users can change themselves
An is-admin flag or a plan name kept in the user's own metadata, or in a profiles row the user is allowed to edit, lets anyone upgrade themselves from the browser. Supabase's own linter treats a policy that reads user-editable metadata as an error. We cover this and six other patterns in broken authentication in AI-generated code.
- 3
Secret keys in the front end
Lovable apps are built with Vite, and Vite ships every variable that starts with VITE_ to the browser. Lovable now moves keys pasted into chat into its Secrets store, but keys added in code, older versions of the app and copies in a connected GitHub repository can still be exposed. The Supabase publishable or anon key is meant to be public; a Stripe secret key, an AI provider key or a service_role key is not.
- 4
Edge functions that trust whoever calls them
Server-side work in a Lovable app runs in Supabase Edge Functions. A function that sends email, calls an AI model or changes a plan needs to check who is calling and what they may do; a valid token alone only proves the request came with one. Functions that receive webhooks need to verify the sender's signature instead.
- 5
Payments that can be unlocked without paying
Plans switched on from the checkout success page rather than from a verified Stripe webhook, webhooks that can be replayed to credit an account twice, and plan limits enforced only in the interface. These are the findings that cost money directly, and they only show up when someone tests the payment flow end to end.
- 6
Fixes that the next prompt quietly undoes
Every change Lovable makes can touch the files that hold your access rules and server code. A policy fixed last week can be loosened today by a prompt about something else, and the Deep scan does not run on its own, only the quicker check that runs at publish. Without a habit of re-checking after big changes, security drifts.
CVE-2025-48757: the Lovable security incident
In March 2025 a researcher scanned 1,645 apps built with Lovable and found 303 endpoints across 170 of them with missing or inadequate row-level security, which let anyone read, and in some cases change, data such as user details, API keys and payment status. It was published as CVE-2025-48757. Lovable disputes the CVE, on the grounds that each customer is responsible for protecting their own app's data, and it now ships the scans above.
The lesson has not changed: the platform will warn you, but the policies are yours. If Supabase or Lovable is showing you a row-level security warning right now, start with what "RLS Disabled in Public" means and how to fix it.
Check your own Lovable app
- 1Open the Security view in your project and run a Deep scan, not only the quick check that runs at publish. Read every finding, including the warnings.
- 2Open More, then Database, then Manage, then Policies (or the policies page in your own Supabase dashboard), and read the policy on each table that holds personal or business data. A policy that says true lets everyone through.
- 3Open the published app in a private window, signed out, and try the pages that should need a login.
- 4Sign up as a second test user and try to open the first user's records by changing IDs in the address bar or in the requests the app sends.
- 5Search the built JavaScript in your browser's developer tools for strings such as sk_live, sk- and sb_secret. Any hit is a key to rotate. A long token starting eyJ should be the anon key; our article on the Supabase anon key shows how to check.
- 6If you take payments, switch Stripe to test mode, buy your cheapest plan with a test card, then refund and cancel it, and check the account ends up in the right state each time.
Security is one half of launching. If you also want to know whether it's ready for real users, including monitoring, backups and separate test and live environments, our production-readiness review covers the rest.
How we review a Lovable app, and what it costs
- Audit, $149, back in 48 hours. A senior engineer reads every policy, edge function and key in the app, tests access as a stranger and as a second user, and checks the payment flow. You get a severity-ranked report in plain English with a fix for every finding.
- Fix Sprint, typically $600 to $1,500, one to two weeks. We fix the critical and important findings, test them again and issue an updated report showing each one closed.
- Production hardening, from $2,500, scoped per project. For apps moving from prototype to a real business: authentication, keeping customers' data apart, payments, monitoring, backups, and anything that genuinely needs rebuilding.
The $149 audit fee comes off the price of whatever you do next, and we sign an NDA on request. The full audit, including what it does not cover, is on the vibe coded app audit page.
We build on the same stack
A Lovable app is a React front end on Supabase. That is how we build too:
- Run Courier: a React, TypeScript and Vite web app plus iOS and Android apps on one Supabase backend, with row-level security, twelve Edge Functions and six role-based dashboards where each role sees only its own data.
- Talent Acquisition platform: a React and Supabase hiring system with row-level security across seven user roles, AI screening and proctored interviews.
Find out what your Lovable app lets people see before they do.
$149, 48 hours, and the fee comes off any fix work you choose afterwards.