It would appear that the XSS that necessitated the release of 3.6.7 extends to another system we did not appreciate at the time of the release.

Therefore, here are a further set of patches and plugins for you to apply.

Here are your options, depending on the version of vBulletin you are currently running.

Currently running vBulletin 3.6.7
Either:

• Download the patch for 3.6.7 from the members' area (or this thread - 367_patch.zip) and upload the contents to your forum directory
• Apply the plugin vb_367_xss_fix_plugin.xml attached to this thread

Those using vBulletin 3.6.7 can make use of the new Patch Level release system, which allows the correct version number to be displayed in the admin control panel - with the patch applied, your version number in the ACP will reflect the fact that you are now running 3.6.7 PL1.

Currently running vBulletin 3.6.4, 3.6.5 or 3.6.6
Either:

• Upgrade to the new vBulletin 3.6.7 package available in the members' area
• Download the patch for 3.6.6 available in the members' area (or this thread - 366_patch.zip) and upload the contents to your forum directory
• Apply the plugin vb_366_xss_fix_plugin.xml attached to this thread

Currently running vBulletin 3.6.x older than 3.6.4
Either:

• Upgrade to the vBulletin 3.6.7 package available in the members' area
• Apply the plugin vb_366_xss_fix_plugin.xml attached to this thread

Once again, we are sorry that this latest problem has occurred. We are looking into ways to ensure that this sort of thing does not happen again.

Please see the original announcement for the patch files: http://www.vbulletin.com/forum/showp...10&postcount=6