Drupal is a leading open source content management tool that hosts a significant portion of the most popular websites on the internet. If you have not heard about the Drupal security flaws from earlier this year, then you need to take a closer look at what happened and start taking precautions to protect your own installations.

A Brief History of Drupal Security Flaws

The first vulnerability was detected in March, according to Drupal, and had the more widespread implications, since everyone running Drupal since v6 could be at risk — potentially affecting a million users. The oldest of these versions is no longer officially supported, yet it is still popular and can be found in production use.

Researchers have also found active automated exploit attempts in the wild, including a new attack method known as Drupalgeddon 2, which places crypto-mining software on unpatched Drupal sites. This means threat actors are scanning IP address ranges to look for vulnerable websites.

The original Drupalgeddon, an SQL-injection vulnerability, was found back in 2014, according to Linux Journal. Drupalgeddon 2 is somewhat similar to its predecessor in that the flaw has to do with another code injection technique involving inputs to web forms that aren’t properly checked, Check Point Research reported. As a result, anyone can navigate to a specific URL on a Drupal-powered website and take it over. There is no authentication required, and once you are in, you have complete control over the site.

Patches for Drupalgeddon 2 were issued for two versions: Drupal 8.3.4 and Drupal 7.56. There have been no known attacks.

How to Protect Your Website

Drupal compiled some recommendations for responding to a site breach that are worth reviewing not just for those tips specific to their software, but for the general implications of keeping your site current and secure.

For example, you should make a forensic copy of your site before applying any changes in case a threat actor has already entered your site. You should also decide whether to roll back or rebuild your servers and determine whom you should notify in case of a breach.

It’s important to note that just patching your server won’t be sufficient in the face of an exploit such as Drupalgeddon. An attacker could have already entered your system and taken complete control over your website. Examining user behavior can also help to identify improper access to site controls.

Drupal’s general suggestions are useful for any website, no matter what code it is running. These include:

• Using multifactor authentication (MFA) to protect your logins. This should be common practice by now, but it bears repeating.
• Using stronger admin passwords. This should also go without saying, but many users are still not employing secure password management.
• Regularly auditing all your user accounts and ensuring that unfamiliar accounts or admin roles haven’t been created by a threat actor.
• Not using an account named “admin” as your administrator’s account. This creates an obvious target.

What Drupal Is Doing to Bolster Security

Drupal has two security projects worth examining. The first is an extension called Paranoia that can block misused Hypertext Preprocessor (PHP) pages and prevent privilege escalation techniques. The second is an older project called Security Review that examines your PHP code for common programming mistakes.

Cybersecurity is an ongoing, iterative process, so conducting code reviews and backing up data should be parts of a continuous audit of your website security. Above all else, security should be a central and ubiquitous pillar of your team’s general operations structure.