Problem Solved
Hi guys, that "exploit" was fixed yesterday (within minutes of when it was reported).
If you're still seeing the error, you've forgotten to authenticate to the site and are seeing cached versions of the error that are, unfortunately, cached by our content delivery network.
Biting the hand that feeds IT
