In one week PHP, WordPress, Drupal and Nginx all shipped security fixes. Why websites need so many updates, a five-question self-check, and two ways out.
- Date
- Reading
- 3 min read
- Written by
- Nick Li
- Tags
- #Web#Risk
On 18 and 19 November, Nginx, WordPress, PHP and Drupal all released security updates, including fixes for flaws that allow remote code execution. Our Alerts page logged several of them in a single week.
If your company website runs a few of these, it may have needed three or four updates in those days. And WordPress's previous security release was only three weeks earlier, on 28 October.
Nobody did anything wrong. Most websites are simply built this way. Below: why websites need constant updates, how to check your own, and two ways to lighten the load.
Why websites need so many updates
A typical company website (built with WordPress, for example) runs several layers of software at the same time:
- Server software (such as Nginx or Apache): receives every visitor's request.
- A programming language (PHP): runs code to build each page whenever someone opens it.
- A content management system (WordPress, Drupal): manages pages and articles.
- Plugins and themes: often more than ten, each maintained by different developers.
- A database (MySQL): stores the content and the accounts.
- A login page: lets admins edit the site, and is the first door attackers try.
Each layer has its own update cycle, and each can have flaws. This week's updates alone covered three of them: Nginx is server software, PHP the language, WordPress and Drupal content management systems. More layers mean more updates to follow, and any one that falls behind can become a way in.
A five-question self-check
1. Does your site have a login page? Try adding /wp-admin or /user/login to your address. If a login page appears, anyone can try to log in.
2. How many plugins does it run? Every plugin is one more piece of software to keep updated.
3. Who installs updates, and how fast? You, a colleague, your host, or the agency that built it years ago? After a security release, attempts to exploit it often start within days.
4. When was it last updated? In WordPress, Dashboard → Updates shows how many items are still waiting.
5. Does the content really change every day? On many company websites it changes a few times a year: the company profile, services, contact details.
Option one: keep updating, properly
If your site needs member logins, online payments or daily content changes, it needs a system running on a server, and updates are part of the job. What you can do is make them routine:
- Turn on WordPress automatic security updates.
- Delete plugins and themes you no longer use.
- Make one person responsible, and check our Patch Tracker and Alerts regularly.
- If you use a hosting company, ask whether they update PHP and the server software for you.
Option two: give attackers fewer ways in
If your site mainly presents your company, services and articles, there is another way: build the site in advance as a set of plain web files and serve them from a content delivery network (CDN). This is called a static website.
There is then no PHP running on the site, no database and no public login page. This week's PHP, WordPress and Drupal flaws have nothing to attack on such a site, because that software doesn't run there. The content can still change; it is simply prepared before publishing instead of being built each time someone visits.
Security doesn't disappear. Your domain and hosting accounts still need strong passwords and two-factor authentication, contact forms should go through a trusted service, and third-party scripts on the site need choosing with care. But the updates to chase drop from several layers to almost none.
What a static site is, how the content is managed and when it doesn't fit are in our earlier article: Why most company websites should be static.
The easiest thing to protect is the thing that isn't there.
If your website mainly presents your company and you'd rather not chase updates every month, talk to us. We can look at which approach suits your site.
