How someone hacked a "course" listing that is porn

How someone hacked a "course" listing that is porn

by Stuart Carduner -
Number of replies: 4
Can you tell me how someone has a "course" listed under my moodle site that is a link to a porn page: http://www.ashokaedu.net/moodle/user/view.php?id=3811&course=1 (sorry, it's not pretty - and obviously it's imperative I remove this)

I am running Moodle 1.7.1 and am now moving to a new server which will be running the latest Moodle. I want to be sure I have removed this stuff so I don't move it to the new site.

I exported the database and in it I found thousands of entries of spam in mdl_cache_text. I emptied the data from this. But i did not find in the database the URL that http://www.ashokaedu.net/moodle/user/view.php?id=3811&course=1actually redirects to (youngtorture.net)

I would appreciate your help or pointer to where this is covered in the forums which I could not find.

Thanks

Average of ratings: -
In reply to Stuart Carduner

Re: How someone hacked a "course" listing that is porn

by Howard Miller -
Picture of Core developers Picture of Documentation writers Picture of Particularly helpful Moodlers Picture of Peer reviewers Picture of Plugin developers
The link that you have supplied is not to a course, it's a user's profile page.

If you are allowing users to register themselves then this is (regrettably) pretty much inevitable. You have to keep a look out for them.

The Spam page is a good place to start.
Average of ratings: Useful (2)
In reply to Howard Miller

Re: How someone hacked a "course" listing that is porn

by Stuart Carduner -
Thanks Just figured that out. Thought I'd checked the profiles already.

Since I have to let people register themselves, what a nightmare!

Thanks
In reply to Stuart Carduner

Re: How someone hacked a "course" listing that is porn

by Howard Miller -
Picture of Core developers Picture of Documentation writers Picture of Particularly helpful Moodlers Picture of Peer reviewers Picture of Plugin developers
You should certainly take a look at enabling "captcha" described in Email-based_self-registration. That might stop a lot of it.
Average of ratings: Useful (3)