dbcve.org
Incorrect AuthorizationWeakness · CWE-863

CVE-2025-48757

CRITICAL · 9.3 CVSS v3.1 Published 2025-05-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An insufficient database Row-Level Security policy in Lovable through 2025-04-15 allows remote unauthenticated attackers to read or write to arbitrary database tables of generated sites. NOTE: this is disputed by the Supplier because each individual customer of the Lovable platform accepts a responsibility over protecting the data of their application.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Insufficient Row-Level Security (RLS) policies in Lovable's database layer allow remote unauthenticated attackers to bypass access controls and read or write to arbitrary database tables within generated sites, effectively giving full database access without credentials.

MitigationThis is a platform-level vulnerability requiring vendor remediation. Organizations should restrict network exposure of generated sites, implement additional authentication layers at the application level, and monitor database access logs for anomalous activity until an official patch is released.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Lovable platform usage
    Identify if your application was generated using the Lovable platform. Check your project documentation, codebase for Lovable-specific imports, or examine the hosting/infrastructure configuration for Lovable service indicators.
    Affected if The site or application was created using Lovable's platform for site generation through April 2025.
  2. Locate database tables in your project
    Examine your database schema to identify all tables that store application data. These are typically found in your database migration files, schema definitions, or ORM configuration files.
    Affected if Your Lovable-generated site uses database tables to store user or application data.
  3. Verify RLS is enabled on tables
    Query your database to check if Row-Level Security is enabled on your tables. For PostgreSQL: SELECT schemaname, tablename, rowsecurity FROM pg_tables WHERE schemaname = 'public';
    Affected if RLS is not enabled (rowsecurity = false) on tables containing sensitive data, or if you cannot verify RLS status.
  4. Inspect RLS policy definitions
    Examine existing RLS policies on your tables using: SELECT policyname, permissive, roles, cmd, qual FROM pg_policies WHERE tablename = 'your_table'; Compare these policies against expected access control requirements.
    Affected if No RLS policies exist, or policies do not properly scope queries to the authenticated user context (e.g., policies that allow unauthenticated or arbitrary access).
  5. Test for unauthenticated data access
    Attempt to query database tables without providing authentication credentials or user context. Check if your application's database connection allows unauthenticated access to arbitrary tables.
    Affected if Database queries can be executed without authentication or user context, returning data from tables belonging to other users or sites.

You are affected if your application was generated on the Lovable platform before the fix date and uses database tables where RLS policies either do not exist or fail to restrict queries to the authenticated user's context, allowing unauthenticated access.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

This is a platform-level vulnerability requiring vendor remediation. Organizations should restrict network exposure of generated sites, implement additional authentication layers at the application level, and monitor database access logs for anomalous activity until an official patch is released.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing12.0 h
  • Review / QA8.0 h
52.0 hours of engineering $9,160
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $14,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-48757 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-48757 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data