🎯A serious flaw in the Lovable app builder lets anyone with a free account see sensitive information from other users' projects, including private data and codes. If you used Lovable to create projects before November 2025, you should change your passwords and security settings right away.
What Happened
A critical Broken Object Level Authorization (BOLA) vulnerability in Lovable, a popular AI-powered app builder platform, has been discovered, allowing unauthorized users to access sensitive project data. This includes source code, database credentials, AI chat histories, and real customer information from thousands of projects created before November 2025. The flaw enables any free-tier Lovable account holder to make unauthenticated API calls to the platform’s backend, retrieving project data belonging to other users.
The Flaw
BOLA vulnerabilities occur when an API grants access to objects without verifying whether the requesting user owns or has permission to view them. This class of flaw is ranked #1 in the OWASP API Security Top 10 for its prevalence and ease of exploitation. A researcher using the handle @weezerOSINT reported that the API endpoint https://api.lovable.dev/GetProjectMessagesOutputBody returns full project message histories, AI reasoning logs, and tool-use records without proper access controls.
What's at Risk
The vulnerability was reported to Lovable via HackerOne approximately 48 days before public disclosure, yet it remains unpatched for projects created prior to November 2025. While Lovable has implemented a fix for newly created projects, legacy projects remain exposed, posing significant risks for users who built applications on the platform before the cutoff date. Notably, one affected project belonged to Connected Women in AI, a nonprofit organization, which contained exposed Supabase database credentials alongside real user data, including records linked to individuals from Accenture Denmark and Copenhagen Business School. Additionally, employees at major technology firms, including Nvidia, Microsoft, Uber, and Spotify, reportedly have Lovable accounts tied to affected projects, raising the stakes for sensitive corporate development data.
Patch Status
The vulnerability was marked as a duplicate on the HackerOne bug bounty platform, indicating that it was already known prior to the latest disclosure on March 3, 2026. Despite this, evidence shows the flaw remains exploitable on legacy accounts, which raises concerns about the effectiveness of the platform's security measures.
Immediate Actions
Security researchers recommend that Lovable users who created projects before November 2025 should immediately rotate any API keys, database credentials, or secrets stored within those projects. Users should assume that chat histories and source code associated with older projects may have already been accessed. This incident highlights a recurring challenge in AI-native development platforms: security controls often lag behind rapid feature deployment, leaving early adopters most exposed. Organizations building production applications on low-code AI builders should enforce secrets management practices independent of the platform and regularly audit API exposure for any sensitive credentials embedded in project repositories or chat contexts.
This incident underscores the importance of robust security measures in rapidly evolving AI development platforms, where the pace of innovation can outstrip security controls.
