Hi,

There is a DotNetNuke security response team see http://security.dotnetnuke.com . You can continue a coversation with myself and other members of the team by sending email to security@dotnetnuke.com When emailing this address, please provide as much relevant detail as you can. Some immediate questions are what version of OS/IIS are you using, and are there any other web sites on the server, is there any unusual activity in your IIS logs, are there any unexpected files on your system, has the default.aspx file been modified, do you have classic asp enabled on your server, and any other detail you think may be relevant.


There is a commonly exploited issue with Microsoft IIS6 that allows for bypassing of extension filtering - Cathal blogged a little on how this could be executed from a DotNetNuke context, but the bug is actually in IIS so it can happen on any similar asp.net code
http://www.dotnetnuke.com/Resources/Blogs/EntryId/2533/IIS6-a-word-of-warning-on-an-issue-affecting-some-websites.aspx . Be sure to check your site for any files name with a .asp; extension followed by another file extension *.asp;.??? (e.g. hacked.asp;.jpg) and remove them.