Re:Persistent XSS on Twitter.com
by b3n on Thursday June 24, 2010 @10:24AM
(#1458087)
It was fixed, but now it's back again...
> The problem is similar to one described last August by James Slater. That time around the issue was with the application URL, this time it appears the application name is the issue.
> The problem is similar to one described last August by James Slater. That time around the issue was with the application URL, this time it appears the application name is the issue.