Learn More





New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Thwarting Registration exploitsThwarting Registration exploits
New Post
1/9/2015 9:57 AM

I am experiencing a spam registration exploit on a site I manage. so far 2500 spam users.

I have followed advice gained from

Resultant Dotnetnuke.config settings:

    <rule servervar="HTTP_URL" values="(?&lt;=\?)ctl=register|(?&lt;!\?)/register" operator="Regex" action="NotFound" location="" />

but the URL still redirects straight to the new registration page.

 What might I have done wrong.

I have also included  denyquerystringsequence configs in the web.config to thwart some of the URLS hitting the site.

          <add sequence="ctl=Register" />
          <add sequence="returnurl=" />
          <add sequence="UserProfile/tabid/324/userId/5066/Default.aspx" />
          <add sequence="register.aspx" />
          <!--added by due to Registration exploit-->


New Post
1/10/2015 3:47 PM

The continuing saga...

I have gone back to the normal system registration page, removed captcha from the form and stopped using the regex filter.  I've left the web.config "ctl=register" denyquerystringsequence string and simply set the registration process to validated.

I also deleted all the spam users so probes using the userID fail.

The problem I have now is thousands of hits from the Bot trying to get in that are clogging up my event log and making normal error tracking unneccesarily difficult.

The probes follow similar patterns, using a userID or calling the register form directly but putting them in the denyquerystring area does not seem to stop them and I don't know what(if anything) to put in the filter

One common one is  


As I've deleted that user, all it generates is a general exception.

I tried adding a denyquerystring sequence
          <add sequence="UserProfile/tabid/324/userId/5066/Default.aspx" />

But it didn't stop it.  Maybe I misunderstand the URL rewrite process.

Has anyone had this problem?

Any solutions/suggestions?


New Post
1/10/2015 9:51 PM

I have the problem.  You are way ahead of me on trying fixes.  I'm trying to get all my sites on the latest 7.3.4 before I tackle the bots.  For now I police the registration and then delete all unauthorized users daily; If I let them in I have to delete them one by one.  I get 50-100 a day.  I simply turned registration off on most sites.


New Post
1/11/2015 6:11 AM

Thanks Bob

If it's any help, I was able to bulk-delete the spam regos by targeting users with a 2-letter country field.

The denyquerystring sequence of ctl=register seems to have stopped any of those attacks and I have had no more successful spam registrations - just a whole bunch of general exceptions which I'd love to waylay somehow.


New Post
1/11/2015 7:25 PM


  What version of DNN are you running?  7.3.4 included some enhancements to return a 404 for non-existent users which should prevent most of your errors from occuring.  You might want to do some testing in QA environment to verify that this version resolves your issue. 

Joe Brinkman
DNN Corp.
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Thwarting Registration exploitsThwarting Registration exploits

These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.

Content Layout

Subscribe to DNN Digest

Subscribe to DNN Digest

DNN Digest is our monthly email newsletter. It highlights news and content from around the DNN ecosystem, such as new modules and themes, messages from leadership, blog posts and notable tweets. Keep your finger on the pulse of the ecosystem by subscribing.  

What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out