Quote Originally Posted by Nekodar View Post
Honestly, considering the timing between when people figured out this method and the fix, I think they knew about it already from internal testing.
Probably didn't consider it so big an issue as to delay the 2.3 release though.
I can see that, I'm just glad it was acknowledged as a serious problem.