All these error messages suck, I'm going to tone back the CSRF protection a bit to fix them. Right now the key changes constantly as you cycle through pages, this seems a little overkill for the problem. As long as you don't go entering the "key=value" from your URL in to any other sites it should be pretty secure with a more static key. I think I'll try just changing it on logins for now, then see if I can write an exploit that will get around it.

I'll be waiting a few days before releasing the source code for the exploit, sorry for the inconvenience of all these error messages. They will be fixed shortly.