>> Site Map >> Forums >> PHP-Nuke Security
Forum module - topics in forum:
PHP-Nuke Security - Been hacked? or have a question about securing your site, here's the place.
PHP-Nuke v7.0 being hacked, how?
I run a site using Nuke 7.0 and a quite often i'll go to check it and i'll find a message in the home module with meta refresh data redirecting me else where.
then when i look up the nuke_athours table i see there is another row added, this is thus giving them superuser access to the site and enableing them to add the message.
My question is a) how is this done? and b) how can i prevent it?
Thanks in advanced Gav
Firstly, I would upgrade your nuke version to 7.6. NOT 7.7+ as this will give you even more security problems then you have now. Download 7.6 and follow the instructions in the upgrade.txt file on how to upgrade without losing your database. I would then download the patched version of 7.6 from here. You would need to replace the required files with the ones from the patched version. Then query your db with the upgradedb.sql file that came with the patched version.
Finally, I would install NukeSentinel, which you can get from here
After you have done the above, you will have a secure nuke site without having to lose any db data.
As always, backup your database before attempting the above.
thanks for that, i'll will install the suggested updates and post here again if i have any further problems.
Thanks Gav
http://phpnuke-uk.net/modules.php?name=Forums&file=viewtopic&t=5624
BL
I have tried to install Nuke v7.6 and all i got is a 500 (Internal Server Error) so i decided to start again, removed nuke v7.0 made a new DB and installed Nuke v7.6; same problem.
Is there anything extra you have to do to install v7.6? or is it a prob with the server itself?
Thanks in advanced, Gav
I have seen this happen where hosting doesnt like .htaccess files
try removing the one in the main nuke root (i.e where your mainfile.php is)If this doesnt solve it try contacting your host because if 7.0 works there's no reason why 7.6 shouldn't.
I have solved the Internal Server Error, it was a permissions error. It shud have been CKMOD should have been 644 but it wasn't.
