This was fixed in the recent security update (IPB.Blog 1.2.3) after an internal audit.

http://forums.invisionpower.com/inde...iew=getnewpost