Ensure that profile properties are correctly filtered

Published: Jan 19, 2011

Version: 1.0

Maximum Severity Rating: Low

Background

DotNetNuke contains support for user profile properties to capture values such as city, state etc., as well as any custom properties required for each user

Issue Summary

Whilst the majority of profile properties encode output, some contain HTML and cannot do so. An additional filter to remove potential XSS issues was added to these profile properties.

Mitigating factors

This only affects sites which display richtext profile properites. The user profile module supports templating so these properties are optional.

Affected DotNetNuke versions

  • 3.0.0-5.6.0

Non-Affected Versions:

  • All other versions

Fix(s) for issue

To fix this problem, you are recommended to update to the latest version of DotNetNuke (5.6.1 at time of writing)

Acknowledgments

Scott Willhite

Security Policy

Click here to read more details on the DotNetnuke Security Policy

Attend A Webinar
Free Demo Site
Download DotNetNuke Professional Edition Trial
Have Someone Contact Me
Have Someone Contact Me

Like Us on Facebook Join our Network on LinkedIn Follow DNN Corporate on Twitter Follow DNN on Twitter

Advertisers

Sponsors

DotNetNuke Corporation

DotNetNuke Corp. is the steward of the DotNetNuke open source project, the most widely adopted Web Content Management Platform for building web sites and web applications on Microsoft. Organizations use DotNetNuke to quickly develop and deploy interactive and dynamic web sites, intranets, extranets and web applications. The DotNetNuke platform is available in a free Community and subscription-based Professional and Enterprise Editions with an Elite Support option. DotNetNuke Corp. also operates the DotNetNuke Store where users purchase third party apps for the platform.