
The problem with vibe coding is simple. You can build something that looks finished before it is actually safe.
AI can create login systems, databases, payment flows, APIs and admin panels very quickly. But a working feature does not mean a secure feature.
The biggest risks are usually:
API keys or passwords left in the code.
Database rules that allow users to see other users’ data.
Weak authentication and permissions.
Admin functions exposed to normal users.
AI-generated code using old or insecure packages.
No limits on APIs, so someone can abuse them.
Payment or webhook logic that trusts data coming from the browser.
Developers deploying code they do not fully understand.
Written by
Edd ITMember12 pieces · 3 followersFollow Edd to see new posts in your feed, on your phone or by email.
More from
Edd IT →Fast to build, fast to disappear
A hosting platform popular with vibe coders is closing down. Zeabur was breached twice in two months, and everything gets switched off by 31 December. The worrying bit: the second time, the attacker…
Whose name is your domain in?
Quick question. If your website disappeared tomorrow, do you know whose name the domain is registered in? A lot of small businesses don't. The domain was bought years ago by a nephew, a freelancer, or the agency…
Nobody tests the backup
Everyone has a backup. Almost nobody has tried to restore one. The hosting says "daily backups included", there's a green tick in a dashboard somewhere, and everyone sleeps fine. Until the day…