Anyone know if this applies to WPTouch 2.x, or is this a vulnerability that only exists in WPTouch 3.x? I'm not using WPTouch on very many sites, but the few that do still use it are using my old 2.x dev license.