404 errors on all backend pages

  • A website I manage was recently hacked. I was able to identify the issues and get the front end back the way it was. However since this happened I get 404 errors on all backend pages. I can login via wp-login.php but it just gives me 404’s for the dashboard and all other admin pages. I have scoured the internet and tried everything from the .htaccess file, permissions, resetting permalinks via PHPAdmin but nothing has fixed the issue. Help me Obi-Wan Kenobi, you’re my only hope.

Viewing 2 replies - 1 through 2 (of 2 total)

  • My recommendation for hacked websites is not to try to restore the system but to import a non-compromised backup. Only there you can be sure that everything works as it should. Based on your description of the state of your website, you can’t even guess what could be broken. Anything can be manipulated during a hack.

    Thread Starter jree300

    (@jree300)

    For anyone else reading this thread experiencing the same problem I wanted to give you an update of what I eventually unraveled and how I was able to regain access to the backend of my client’s website.

    The hack was server wide. They used code in certain PHP files like the index.php file and a few others they created to continually regenerate their modified .htaccess file which denied access to PHP files. Every time I modified the .htaccess files via FTP they would automatically revert back. Once I hunted down the PHP files with malicious code and either deleted the malicious code (in the case of the index.php file) or deleted the PHP file altogether (in the case of the php files that were not legit PHP files) I was able to modify the .htaccess files to no longer deny access to PHP, thus eliminating the 404 errors. They placed these files in not only the particular website directory but also in the root public_html folder and various other places on the server. Many files were modified or added by the hackers but I was able to track them down by doing an FTP server search using Filezilla, using the “last modified date”.

    I hope this is helpful for anyone else experiencing a similar problem. Feel free to ask any questions regarding this if you are experiencing the same issue and I will be glad to share any information I can to how I remedied this problem.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘404 errors on all backend pages’ is closed to new replies.