Multiple vulnerabilities have been reported in DotNetNuke, which can be exploited by malicious users to disclose potentially sensitive information, bypass certain security restrictions, and conduct script-insertion attacks and by malicious people to bypass certain security restrictions and conduct cross-site scripting attacks.

1) Input passed to the "__VIEWSTATE" parameter in Install/InstallWizard.aspx is not properly sanitised before being returned to the user. This can be exploited to execute arbitrary HTML and script code in a user's browser session in context of an affected site.

This vulnerability is reported in versions 3.0.0 through 5.6.0 and confirmed in version 5.06.00 (Community Edition).

2) The application provides an error page when a module installation or upgrade fails, which may disclose e.g. the host operating system.

This weakness is reported in versions 5.0.0 through 5.6.0.

3) An error allows a user with "edit" permissions to access modules' settings. This can be exploited to grant additional granular permissions to the user.

This security issue is reported in version 5.6.0.

4) Certain unspecified input is not properly sanitised before being returned to the user. This can be exploited to execute arbitrary HTML and script code in a user's browser session in context of an affected site.

This vulnerability is reported in versions prior to 5.6.1.

5) The application provides overly detailed information when the password recovery mechanism is used. This can be exploited to e.g. enumerate valid users.

Successful exploitation requires that "enablePasswordRetrieval" is enabled.

6) Certain user profile properties are not properly sanitised before being used. This can be exploited to insert arbitrary HTML and script code which will be executed in a user's browser session in context of an affected web site when the malicious data is being viewed.

These vulnerabilities are reported in versions 3.0.0 through 5.6.0.

7) The application incorrectly enforces access restrictions to certain pages' functionality. This can be exploited to e.g. compromise a vulnerable system by installing a malicious module.

Successful exploitation requires that the ViewState is not encrypted.

This security issue is reported in versions 5.0.0 through 5.6.0.

Solution
Update to version 5.6.1.

Provided and/or discovered by
1) Richard Brain, ProCheckUp Ltd
2) The vendor credits Brandon Haynes.
3) The vendor credits David Lee and Roger Selwyn.
4) The vendor credits Chris Wood.
5) The vendor credits Andrew Hallmark.
6) The vendor credits Scott Willhite.
7) Daniël Niggebrugge, Fox-IT BV

Changelog
Further details available to Secunia VIM customers

Original Advisory
DotNetNuke:
http://www.dotnetnuke.com/News/securitybulletinno45/tabid/2112/Default.aspx
http://www.dotnetnuke.com/News/SecurityPolicy/securitybulletinno46/tabid/2113/Default.aspx
http://www.dotnetnuke.com/securitybulletinno47/tabid/2114/Default.aspx
http://www.dotnetnuke.com/News/SecurityPolicy/securitybulletinno48/tabid/2115/Default.aspx
http://www.dotnetnuke.com/News/SecurityPolicy/securitybulletinno49/tabid/2116/Default.aspx
http://www.dotnetnuke.com/News/SecurityPolicy/securitybulletinno50/tabid/2117/Default.aspx
http://www.dotnetnuke.com/News/SecurityPolicy/securitybulletinno51/tabid/2118/Default.aspx

PR10-19:
http://www.procheckup.com/vulnerability_manager/vulnerabilities/pr10-19

Fox-IT:
http://www.fox-it.com/en/news-and-events/news/recent-news/news-article/dotnetnuke-remote-code-execution-vulnerability-discovered-by-fox-it/174

Deep Links
Links available to Secunia VIM customers