How to fix Drupalgeddon2 vulnerability (CVE-2018-7600) in Drupal 7.x and 8.x

On March 28th, Drupal disclosed a Highly Critical vulnerability in Drupal core (CVE-2018-7600) that was dubbed Drupalgeddon 2 (Drupalgeddon 1 happened in 2014)

Drupal version 7.x and 8.5.x was affected by this vulnerability, and allowed remote attackers to infect the site with malicious code.

If you think your site is hacked or might be vulnerable, click here to consult our Drupal Security Experts. We’ll patch your site, and if needed restore your site from backups.


Here at Bobcares Website Management Serivces, we help website owners keep their applications and servers secure.

Within hours of the security notification, we applied the official patches to keep the sites of our customers safe.


Drupalgeddon 2 exploits in the wild

Usually immediately after a vulnerability is disclosed, we get reports of sites being compromised.

For this vulnerability, all seemed quiet for 2 weeks. And then it started.

Since April 15, we started getting website recovery requests from website owners at our On-demand Emergency Support channel. This channel serves web site owners who are not our service subscribers, but need on-demand support.

We found many of these sites with malware uploaded into them, and malicious processes running off it (backdoors, crypto currency miners, etc.).

There were some sites which didn’t have any trace of malware, but we assume that the server is infected if the site was not patched before the first automated attacks started (on April 11th).


How to fix Drupalgeddon 2

The best path to take is to:

  • Backup and delete the current website.
  • Restore a previous version of the site from backup.
  • Apply the patches
  • Upgrade Drupal to the latest version.


However, there may be sites that might not have a recent backup.

For these sites, we recreate the hosting account by manually weeding out changed files, and restoring the site by hand.

It is not a 100% fool-proof method, but it is a reasonably sure way to get rid of files that might be infected.

If your site is hacked or feel it might be infected, click here to consult our Drupal Security Experts.


What if I have Drupal 6?

Drupal 6 reached End of Life in Feb 2016, and no new patches are available for over 2 years now.

So, if you have a Drupal 6 website, we’d recommend you to upgrade your site with the help of our Drupal Development team.

We’ll manually verify each file and migrate your site to a Drupal 8 platform.

Click here to get a custom quote.


How to keep Drupal safe

Drupal is a reasonably secure platform, but like any other web application, it get affected by vulnerabilities.

We keep our customer’s Drupal sites safe by:

  • Monitoring for vulnerabiltiies 24/7 and applying emergency patch within hours of a disclosure.
  • Updating Drupal core, themes and modules within a few days of their release.
  • Hardening Apache, Nginx, PHP and MySQL to prevent malware execution on the server.
  • Blocking malware uploads by using custom configured Web Application Firewalls.
  • Hardening the Filesystem and Network to make sure poor reputation IPs cannot connect to the server, and download malware into the server.
  • Scanning the server media and processes for malicious acitivity, and weeding out malware within minutes if manages to get through the defenses.


If you have a Drupal website, click here to know how we can help you keep it secure and fast.



If you think your site is hacked or might be vulnerable, click here to consult our Drupal Security Experts. We'll patch your site, and if needed restore your site from backups.


Submit a Comment

Your email address will not be published. Required fields are marked *

Bobcares is a server management company that helps businesses deliver uninterrupted and secure online services. Our engineers manage close to 51,500 servers that include virtualized servers, cloud infrastructure, physical server clusters, and more.

Related Posts

Privacy Preference Center


Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]


Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid


Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie

Close your account?

Your account will be closed and all data will be permanently deleted and cannot be recovered. Are you sure?