CVE-2025-48757VulnerabilityPublished 30 May 2025

CVE-2025-48757: Lovable · Incorrect Authorization

Affects LovableSource CVE Database V5

Not known to be exploited · CVSS 9.3 Critical.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

9.3Critical

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.8% chance of exploitation in 30 days – higher than 57% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Changed
Confidentiality: High
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 30 May 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Lovable Lovable	Affected =0	Fixed in–

AI-suggested

To mitigate this vulnerability effectively, European organizations should: 1) Immediately apply any available patches or updates from Lovable once released. 2) Implement compensating controls such as network segmentation and firewall rules to restrict external access to Lovable database servers, limiting exposure to trusted internal networks only. 3) Conduct a thorough audit of current RLS policies and database permissions to ensure strict enforcement of access controls, verifying that no unauthorized read/write permissions exist. 4) Employ database activity monitoring tools to detect anomalous queries or unauthorized access attempts in real-time. 5) Consider deploying Web Application Firewalls (WAFs) with custom rules to block suspicious requests targeting Lovable endpoints. 6) Review and enhance logging and alerting mechanisms to ensure rapid detection and response to potential exploitation attempts. 7) Educate IT and security teams about the vulnerability specifics to increase vigilance. 8) If feasible, temporarily disable or restrict features of Lovable that expose database access until a patch is applied. These steps go beyond generic advice by focusing on immediate risk reduction through network and database controls and proactive monitoring.

Description

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.

Impact

For European organizations using the Lovable platform, this vulnerability poses a severe risk to data confidentiality and integrity. Unauthorized access to sensitive or regulated data could lead to violations of the EU General Data Protection Regulation (GDPR), resulting in substantial fines and reputational damage. The ability for unauthenticated attackers to manipulate database contents could disrupt business operations, corrupt critical data, or facilitate further attacks such as privilege escalation or lateral movement within the network. Industries with stringent data protection requirements, such as finance, healthcare, and public sector entities, are particularly vulnerable. Additionally, the breach of generated sites' databases could expose customer information, intellectual property, or internal business data, undermining trust and potentially causing financial losses. The lack of authentication requirement and the remote exploitability increase the likelihood of exploitation attempts, especially in environments where Lovable is exposed to the internet without adequate network-level protections.

CWE-863Incorrect Authorization (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #17OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.
Architecture and Design
Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries.
Architecture and Design
Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
V7.2.2 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 7 Jul 2025, 21:40 UTC

WeaknessesCWE-863

Technical details

References

Community reviews

Related threats