Title: Website Comprimised Last modified: September 30, 2020 --- # Website Comprimised * Resolved [ACEuser](https://wordpress.org/support/users/aceuser/) * (@aceuser) * [5 years, 8 months ago](https://wordpress.org/support/topic/website-comprimised/) * Good Afternoon, * So I logged into our website to find that Wordfence had been deactivated. I re- activated it, and started a scan and it found these files: * vars.php – Modified Official File skirt.php Jcrop.php class.wp-includes.php wp-widgets.php * I have cleaned up the website by FTP, so I am fine for now, but I am at a loss as to why my website is compromised. There are only 2 users, each with strong passwords, along with our database with a strong password, and our file permissions set to 644 through FTP. * Is there a vulnerability within wordfence lately? * There doesn’t appear to be any users created out of the blue, and only 1 of the official users logged in, and last login was 9/12. The files I found showed they were added 9/17. Viewing 1 replies (of 1 total) * Plugin Support [WFAdam](https://wordpress.org/support/users/wfadam/) * (@wfadam) * [5 years, 8 months ago](https://wordpress.org/support/topic/website-comprimised/#post-13480439) * Hello [@aceuser](https://wordpress.org/support/users/aceuser/) and thanks for reaching out to us! * I am sorry to hear that you are experiencing this. I will explain in more detail some possible scenarios of how a hacker can gain entry and why a site becomes compromised – even if you are very meticulous at keeping your server software, WordPress, your active and inactive plugins and themes all up to date with the latest versions. * Some causes of a hack are impossible for any WordPress security plugin to protect against: 1) If you are using a weak password for your hosting account control panel or FTP account then a hacker may gain entry this way, with full access to your site’s file system and database. 2) You are storing unmaintained, unarchived backups of your site that are publicly accessible that contain exploitable vulnerabilities. 3) You are hosting more than one PHP application, such as more than one installation of WordPress, in the same hosting account and infection can spread from another application to this site. 4) You have unmaintained or vulnerable 3rd party scripts installed in your hosting account. Examples would be the Adminer or SearchReplaceDB database management tools. 5) A nulled theme or plugin with malware already pre- installed. If you paid for a theme or a plugin outside of the vendor’s website at a massively reduced price, that seemed too good to be true, then it is likely to be nulled. 6) If you are using a shared hosting account a neighboring account can be infected and spread the infection to this site. 7) Your WordPress wp-config. php configuration file could be readable to the hacker, either directly via your hosting account, via a vulnerable plugin, or via another hacked site on the same server. 8) The hosting accounts on the server may not be properly isolated so the hacker has access to your database via another user’s database. 9) The server software has vulnerabilities that allow the hacker to get root access – such as running an end-of-life version of PHP on the hosting server that has unpatched vulnerabilities. 10) If the hack took place at a time when you only had the free version of Wordfence installed then you wouldn’t have had access to the latest firewall rules that premium customers have access to. 11) You may be using a plugin or theme with a vulnerability that is so severe that Wordfence can not protect against it and we may be unable to create a custom firewall rule for the vulnerability. However, being unable to create a custom firewall rule is very rare. * Wordfence protects against a vast variety of attacks. Whether you were hacked because of an unknown attack method or because there is some other issue in your system impossible to say at this stage without an extensive investigation. There are some aspects of your site security that are completely beyond our control such as vulnerabilities on your hosting server as described above. Although rare, for examples of hosting provider vulnerabilities please see these two articles below: [https://www.wordfence.com/blog/2019/06/service-vulnerability-four-popular-hosting-companies-fix-nfs-permissions-and-information-disclosure-problems/](https://www.wordfence.com/blog/2019/06/service-vulnerability-four-popular-hosting-companies-fix-nfs-permissions-and-information-disclosure-problems/) [https://www.wordfence.com/blog/2018/02/service-vulnerability-nfs-permissions-problem/](https://www.wordfence.com/blog/2018/02/service-vulnerability-nfs-permissions-problem/) * Hope this helps! * Thanks! Viewing 1 replies (of 1 total) The topic ‘Website Comprimised’ is closed to new replies. * ![](https://ps.w.org/wordfence/assets/icon.svg?rev=2070865) * [Wordfence Security - Firewall, Malware Scan, and Login Security](https://wordpress.org/plugins/wordfence/) * [Frequently Asked Questions](https://wordpress.org/plugins/wordfence/#faq) * [Support Threads](https://wordpress.org/support/plugin/wordfence/) * [Active Topics](https://wordpress.org/support/plugin/wordfence/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/wordfence/unresolved/) * [Reviews](https://wordpress.org/support/plugin/wordfence/reviews/) * 1 reply * 2 participants * Last reply from: [WFAdam](https://wordpress.org/support/users/wfadam/) * Last activity: [5 years, 8 months ago](https://wordpress.org/support/topic/website-comprimised/#post-13480439) * Status: resolved