vBulletin 3.6.7 has been released, just a couple of days after the 3.6.6 release....
Below is a copy of the post from vbulletin.com.

The good news is that there are NO TEMPLATE CHANGES!
All of the current vBulletin 3.6.6 Skins will work flawlessly with this new version. :Waldo:


New customers will need to check the yes "Ignore Style Version - Use style file even if it was created by a different version of vBulletin?" when importing the skins.



Current customers that are upgrading and have already installed the skin do not need to upgrade the skins.



Quote Originally Posted by vBulletin.com
vBulletin 3.6.7

The 3.6.7 package has been updated as of 18:30 UTC, May 16th 2007

As much as we hate to spring another upgrade on you all so soon after the release of vBulletin 3.6.6, an XSS flaw was identified today and in order to maintain our commitment to fix security problems as soon as we become aware of them, we have to release 3.6.7 and a patch for older versions.

All versions of vBulletin 3.6 prior to 3.6.7 are vulnerable to the XSS. vBulletin 3.5.x and 3.0.x are not affected.

To minimize the pain of another upgrade, there are no changed templates since 3.6.6 and no database schema changes, so the upgrade should be as simple and quick as possible.

Since we have fixed several bugs since vBulletin 3.6.6 was released, these fixes are also incorporated in this version and include amongst others:A complete list of bugs fixed in the 3.6 branch is available in the project manager.

Please accept our apologies for bringing out a new version just days after the previous release. We're sorry.

Fixing the XSS Bug

The XSS problem can be resolved in one of three ways.
  1. Full Upgrade: The best way to fix the problem is to perform a full upgrade, downloading the complete 3.6.7 package from the vBulletin Members' Area and following the regular upgrade instructions. This is the only option that will not only fix the XSS issue, but will also apply all the bug fixes made since the release of 3.6.6.
  2. Patch: A second option is to download the patch files either in the Members' Area or attached to this thread and upload them to your web server, overwriting the existing files.
    Patch file: 366_patch.zip
  3. Plugin: The plugin system built into vBulletin 3.6 allows the problem to be fixed with a simple plugin. The install file for this plugin is also attached to this thread and is the easiest way to fix the problem, as it does not require you to upload any files via FTP. The plugin will be automatically removed when you perform your next full upgrade. You can install the plugin by following the instructions here.
    Plugin File: vb_calendar366_xss_fix_plugin.xml
Please note the following:
  • The plugin can be used with any previous version of vBulletin 3.6
  • The patch can only be applied to vBulletin 3.6.4, 3.6.5 or 3.6.6
  • You may perform a full upgrade to vBulletin 3.6.7 from any previous version of vBulletin 3.