See this, this and this. It doesn't just impact 3.3, 3.2.9 is also affected.
What concerned me is this site doesn't have the issue fixed. Which doesn't inspire a lot of confidence in upgrading to 3.3. Good to know there's fixes for it even if the admins here didn't implement it personally.