You've spent 5 hours now raging against this "mistake".

A mistake that you didn't realize is only rolled out on their testing instance.

You have more than one dev stating they are aware of it and it's on the list to be addressed later, despite claiming you had no way of knowing that. You do as of a decent number of hours ago.

You have another dev stating that this thing you think is a horrible development failure would require DB access to exploit in the way you hypothesized. Together with this only being in the bleeding edge test instance, this invalidates the overwhelming majority of your complaints.

And then you have the sheer balls to tell another commenter their comment was worthless, as it was too much speculation? Your entire fucking thrust is based off not just speculation, but a critical misunderstanding of the situation.

If you have the development background you claim, go make a fucking pull request. I normally hate that sort of shit, but after you've pulled the shit you've pulled in these comments, throwing your dick around like some sort of hotshot?

Put your money where your mouth is.

I've only got ten years experience, mostly in IT infrastructure admin/engineering, but one of the biggest lessons I learned early was to save my criticism until I actually understood what was going on. Another big one was to just not be a dick bag. And to apologize instead of doubling down when I was shown I was wrong.

I guarantee that if you bring this kind of attitude to work, the only reason you've lasted is because you're on a large team. You'd be out in the first month at any of the (smaller) places I've worked.