DotNetNuke Unauthorized Access Vulnerability



Date Discovered

November 22, 2019


DotNetNuke is prone to an unauthorized-access vulnerability. Attackers can exploit this issue to gain unauthorized access and perform unauthorized actions. This may aid in further attacks. DotNetNuke versions 7.0.0 through 9.3.2 are vulnerable.

Technologies Affected

  • DotNetNuke DotNetNuke 7.0.0
  • DotNetNuke DotNetNuke 7.0.1
  • DotNetNuke DotNetNuke 7.0.2
  • DotNetNuke DotNetNuke 7.0.3
  • DotNetNuke DotNetNuke 7.0.4
  • DotNetNuke DotNetNuke 7.0.5
  • DotNetNuke DotNetNuke 7.0.6
  • DotNetNuke DotNetNuke 7.1.0
  • DotNetNuke DotNetNuke 7.1.1
  • DotNetNuke DotNetNuke 7.2.2
  • DotNetNuke DotNetNuke 7.4.0
  • DotNetNuke DotNetNuke 7.4.1
  • DotNetNuke DotNetNuke 8.0
  • DotNetNuke DotNetNuke 8.0.1
  • DotNetNuke DotNetNuke 9.0.0
  • DotNetNuke DotNetNuke 9.1.0
  • DotNetNuke DotNetNuke 9.1.1
  • DotNetNuke DotNetNuke 9.2.0
  • DotNetNuke DotNetNuke 9.2.1
  • DotNetNuke DotNetNuke 9.2.2
  • DotNetNuke DotNetNuke 9.3.0
  • DotNetNuke DotNetNuke 9.3.1
  • DotNetNuke DotNetNuke 9.3.2


Block external access at the network boundary, unless external parties require service.
If global access isn't needed, filter access to the affected computer at the network boundary. Restricting access to only trusted computers and networks might greatly reduce the likelihood of successful exploits.

Run all software as a nonprivileged user with minimal access rights.
To reduce the impact of latent vulnerabilities, always run nonadministrative software as an unprivileged user with minimal access rights.

Deploy network intrusion detection systems to monitor network traffic for malicious activity.
Deploy NIDS to monitor network traffic for signs of anomalous or suspicious activity. This includes but is not limited to requests that include NOP sleds and unexplained incoming and outgoing traffic. This may indicate exploit attempts or activity that results from a successful exploit.

Updates are available. Please see the references or vendor advisory for more information.



The vendor reported this issue.

© 1995- Symantec Corporation

Permission to redistribute this alert electronically is granted as long as it is not edited in any way unless authorized by Symantec Security Response. Reprinting the whole or part of this alert in any medium other than electronically requires permission from


The information in the advisory is believed to be accurate at the time of publishing based on currently available information. Use of the information constitutes acceptance for use in an AS IS condition. There are no warranties with regard to this information. Neither the author nor the publisher accepts any liability for any direct, indirect, or consequential loss or damage arising from use of, or reliance on, this information.

Symantec, Symantec products, Symantec Security Response, and are registered trademarks of Symantec Corp. and/or affiliated companies in the United States and other countries. All other registered and unregistered trademarks represented in this document are the sole property of their respective companies/owners.