On Wed, May 7, 2008 at 2:51 PM, Richard Dahl <[EMAIL PROTECTED]> wrote: > Excellent, good catch, when logged out it does indeed display the > alert, I image it has to do with the 'next' property, which is not, I > believe, escaped, as it is not entered into the DB or presented to any > other user. So again, it begets the question: How is the XSS attack > possible?
I'd imagine the big threat is actually not "scripting" per se, but the fact that you can tweak the URL that form submits to for a non-logged-in user. That user then, you hope, ignores the glaring warning of the URL and submits username/password to wherever you want him/her to send it. Easily prevented by users who have half a brain, but still needs fixing. I've cross-posted to django-dev to get it handled. -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
