Static Host UK

What Static Hosting Can't Fix: Your Supabase Rules and Exposed Keys

In 2025 a researcher found 170 Lovable apps whose databases answered anyone who asked. The fix lived in Supabase, and no web host could have made it.

By , founder and sysadmin of Static Host UK

I'm Axel Segebrecht. I build privacy-first platforms, advise small businesses on AI governance, and create free tools for the neurodiverse community.

Static hosting removes the web server from the list of things an attacker can go after. Many AI-built sites keep their data somewhere else, and nothing about how we serve your pages protects it. This post is about that part.

What happened

In March 2025 Matt Palmer scanned the home pages of 1,645 sites built with Lovable. On 170 of them, about one in ten, the database behind the site handed out data it should have refused: 303 endpoints in all, exposing names, phone numbers, API keys and payment details (Palmer’s statement). 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.

The way these sites are built explains it. The pages run in the visitor’s browser and talk straight to a Supabase database, using a key that ships inside the page. What stands between that key and your data is a set of rules in the database called Row Level Security (Palmer’s write-up).

The key in your page is meant to be public

Supabase says so plainly. The publishable key, once called the anon key, goes in anything you ship, and “anyone can read it, so it only reaches what Row Level Security allows”. The secret key bypasses those rules and “must never leave your control” (Supabase API keys).

So a visible key is normal. A table with no rules is the problem: “A table in an exposed schema without RLS is readable and writable by any role with a grant on it” (Supabase Row Level Security).

What moving your front end changes

The pages: they become files on our servers, sent with the security headers from yesterday’s post.

The database: nothing. Whether the front end lives on Lovable, with us or anywhere else, the browser still talks to Supabase directly, and Supabase still answers according to your rules.

What to check

  • In Supabase, confirm Row Level Security is on for every table in the public schema.
  • Read each policy and ask who it lets in. A policy written using (true) lets in everyone it applies to.
  • Search your repository for the secret key. If it appears anywhere in code that reaches the browser, rotate it.
  • If you built with Lovable, run its security scan, and review the policies yourself even when it reports nothing. That is Palmer’s advice too.

Do these checks before you move an AI-built site anywhere, including to us.

get started

Ready to Deploy?

Join Jamstack developers across the UK hosting their static sites with privacy and performance built in. Hosting is free for good, no credit card needed, with Plus features when you want them.