Skip to main content
Mallory
CriticalPublic exploitVulnerability

CVE-2025-48757: Insufficient Database Authorization in Lovable-Generated Applications

Published May 30, 2025 · Updated 11 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days3 mentions · peak 1 in a dayToday
CVSS9.3Critical · v3.1
EPSS0.83%59th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
IdentifiersCVE-2025-48757CWE-863 · Incorrect Authorization

CVE-2025-48757 is an authorization weakness affecting applications generated by Lovable through April 15, 2025. Missing or insufficiently restrictive Row-Level Security (RLS) policies in associated Supabase databases allow remote unauthenticated attackers to read or write arbitrary exposed database tables. Supabase's public client-side anonymous key does not provide user-level authorization; access restrictions depend on correctly configured database policies. Lovable disputes the vulnerability's attribution to its platform, stating that individual customers are responsible for protecting their applications' data.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation compromises the confidentiality and integrity of affected application data. Exposed information can include names, email addresses, financial information, and secret API keys. Unauthorized writes allow attackers to modify records or inject malicious data into tables permitted by the defective configuration. Exposure of usable secrets may enable additional unauthorized access, depending on those secrets' privileges. Code execution and availability impact are not established.

Mitigation

If you can’t patch tonight, do this now.

Until authorization policies are corrected, disable unnecessary public database access or remove anonymous-role permissions from sensitive tables. Audit other tables in the same project for equivalent exposure. Review accessible records for unauthorized modifications and rotate any secret API keys or credentials that were exposed. Public Supabase anonymous keys are not substitutes for RLS and should not be treated as secret authorization credentials.

Remediation

Patch, then assume compromise.

Enable RLS on exposed Supabase tables and implement restrictive policies that enforce the application's intended authorization rules for both reads and writes. Review existing policies rather than relying solely on whether RLS is enabled, and validate access using anonymous and authenticated roles. Explicitly check programmatically created tables, because tables created through the Supabase API do not have RLS enabled by default. No specific fixed Lovable release is identified.

Public exploits

Exploits

No validated public exploits yet. Hidden: 5 rejected by Mallory's analysis as not a working exploit.

View more in app →
Every candidate exploit was rejected by Mallory's analysis.
FAQ

Frequently asked questions

Is CVE-2025-48757 exploited in the wild?
As of Nov 11, 2026, Mallory has no reports of CVE-2025-48757 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2025-48757?
Yes. As of Nov 11, 2026, Mallory has reports of a public exploit for CVE-2025-48757.
Is there a patch for CVE-2025-48757?
Enable RLS on exposed Supabase tables and implement restrictive policies that enforce the application's intended authorization rules for both reads and writes. Review existing policies rather than relying solely on whether RLS is enabled, and validate access using anonymous and authenticated roles.
How severe is CVE-2025-48757?
CVE-2025-48757 has a CVSS v3.1 score of 9.3 (Critical) and an EPSS score of 0.83% (59th percentile) as of Nov 11, 2026.
Activity feed

Recent activity

14 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity10Community discussion across Reddit, Mastodon, and other social sources.