Yes, I know just about every post I found on the problem, says to upgrade, and I'm planning to as soon as VB3 is released. I have heard people say that there is a workaround/patch at vb.com in the announcement forum, but the closes thing I could find was this post:
http://www.vbulletin.com/forum/showt...threadid=57203
that links to another that still didn't fix the problem. Unfortunantly I couldn't run a search at vb.com because XSS is only 3 letters and VB.com requires at least a 4 letter word for the search.
Can somebody direct me to the correct XSS thread at vb.com to get a temporary fix for my site?
Thanks.