Anyone that's used the PHPNuke for the content management of their website might have heard about all of the security holes occurring in some of the latest versions, and you're a bit concerned. So, what happens if someone does use one of those holes - how do you get back into control? Well, this new DevShed article seeks to help you do just that.

They take a preventitive approach to the matter, showing you where the common bugs might be, and how to patch them/watch them so that no one gets any bad ideas. Once the site is hacked, there's only so much you can do to wrestle back control from the responsible parties, but if done correctly, it will stop them dead in their tracks every time.

Once you're back in control, then begins the cleanup, removing the traces the perpitrator left behind. Finally, they mention a tool that you can use in the future to keep this from happening again - The Protector System for PHP-Nuke. It makes attempts to protect your PHP-Nuke installation from all types of SQL-Injection Attacks, Get/Post Attacks and Hammer Attacks. It also automatically blocks or bans users by username or IP address when they try attacking your site using these known methods. Definiately a helpful tool for this popular CMS.