PHP2Shell: two critical PHP flaws, and when our servers got the fix
Two critical flaws in PHP itself were fixed on 21 October. Every website we host has run the fixed PHP since 02:59 UTC on 22 October. There is nothing for you to do.
Keeping your websites, accounts and data safe.
Two critical flaws in PHP itself were fixed on 21 October. Every website we host has run the fixed PHP since 02:59 UTC on 22 October. There is nothing for you to do.
Roundcube, the software behind webmail.maxinodes.com, fixed 20 security flaws on 19 October. Our webmail installed the update by itself that night. There is nothing for you to do.
By 2029 no certificate will last more than 47 days, and September's attacks on three country domains showed why. Who has to act, and how to see every certificate for your domain.
WordPress fixed a serious flaw on 22 September and attacks began that day. Update to 7.1.2. We've turned off a PHP setting the known attack needs; only the update fixes the flaw.
A broken backup is usually discovered on the day it is needed. Five questions to ask your host, a fifteen-minute test, and what we found when we ran it on our own platform.
Between 27 August and 14 September, three flaws were published in cPanel and LiteSpeed that let a single account on a shared server take control of the whole machine. All three are fixed on our servers, and there is nothing for you to install or change. Here is when each fix went in.
The plugin most people use to move a WordPress site has a serious flaw in the part that restores a backup, fixed in version 7.110. If you installed it for a move and never opened it again, it is still there.
A server in Europe does not make your hosting GDPR-compliant by itself. Seven questions and three documents separate hosts that can back the claim from hosts that just put it on the homepage.