Of course, because the fix is completely irrelevent to CVS-2007-6318, which is not fixed even after WordPress 2.3.3. The fix is against another vuln instead:
http://xforce.iss.net/xforce/xfdb/39409
I don't know how wrong and how far does this advisory go though.
Of course, because the fix is completely irrelevent to CVS-2007-6318, which is not fixed even after WordPress 2.3.3. The fix is against another vuln instead:
http:// xforce. iss.net/ xforce/ xfdb/39409
I don't know how wrong and how far does this advisory go though.