Vibe-Coded Apps: When to Patch Security or Rebuild ProperlyVibe-Coded Apps: When to Patch Security or Rebuild Properly
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Anyone on the internet could spend my client's money.
No login. No limit. One AI endpoint in his Replit-built app, wide open, running on his OpenAI and Gemini bill.
The fix took 5 minutes. Finding it took a full audit.
It was one of 17 security issues in an app that "worked fine." That's vibe coding. A study of 200 live vibe-coded apps found 91% had at least one vulnerability. The app works. That's exactly why nobody looks.
Here's the part people get wrong though. We didn't rebuild it. His idea wasn't validated yet and the budget was tight. So we fixed security first, then the code vulnerabilities, then brought in QA to hunt bugs one by one.
Another founder came to us with a Bolt app and two months of proven demand. We opened the codebase and didn't patch a thing. We started over. Me, a dev, a QA, 15 weeks, production-ready.
Same problem. Opposite calls. Both right.
Unvalidated idea? Fix what can hurt you and go find customers. Validated idea? Rebuild it properly.
Built something on Lovable, Bolt, Replit or Cursor and not sure which camp you're in? DM me.
Post image
Back to feed
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started