This comment was completely tongue in cheek; in all seriousness it was great to see them fix this so quickly.

Tell me that blog post didn't read like a security exploit announcement...

Anyways, as discussed, it never should've happened in the first place, but it sounds like from the comment threads that it was likely Framework related, so.... yeah, still prettty bad.