65
Vibe Coding Has a Security Problem Nobody Wants to Talk About
(mothasa.substack.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 23 Feb 2026
65 points (86.5% liked)
Programming
25806 readers
266 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 2 years ago
MODERATORS
The article says:
but I've seen exactly this. After years of not seeing any SQL injection vulnerabilities (due to the large increase in ORM usage plus the fact that pretty much every query library supports/uses prepared statements now), I caught one while reviewing vibe-coded code ~~written~~ generated by someone else.
Forget SQL injection and XSS, LLMs are bringing back unsanitised inputs as a whole, including reintroducing previously removed vulnerabilities. You can casually browse Github for submissions by Claude bot and find ../.. vulns all over.
Yes. And let's not forget bringing back the classic "forgot to even put a password on the sensitive files".
“Someone else” “writes” vibe-coded code in the same way that someone buying a meal at a restaurant cooks said meal.
Haha good point - maybe "generated by" is a better description?