Drupal 7 has reached end of life: how to protect the sites still running it

Drupal 7 support ended on 5 January 2025, yet according to drupal.org almost a third of Drupal sites still use it. Until the migration is ready, those sites need closer watching than the others.

New vulnerabilities will stay open.

Every flaw found in Drupal 7 from now on gets no official fix. It is the CMS hit by Drupalgeddon and Drupalgeddon2, and attackers still look for these sites.

The 2014 Drupalgeddon malware hid in the database, in the menu_router table, where a file scan never looks.

A module built for Drupal 7.

  1. Install the Drupal 7 module

    Same machine name as the module for Drupal 8 and later, written to run even on PHP 7.1.

  2. Watching

    Core integrity against the official archive, new administrators, suspicious files, dangerous callbacks in menu_router, PHP filter module enabled.

  3. Backups and migration

    Regular encrypted backups and the end-of-life alert, until the site moves to a supported release.

Want to try it on a real site? The 30-day trial needs no credit card.

Start free trial

Frequently asked questions

Is Drupal 7 still supported?

No. Official security fixes ended on 5 January 2025. Plan the migration to Drupal 10 or 11.

Does the module run on PHP 7.1?

Yes, the Drupal 7 module runs even on PHP 7.1, encrypted backups included.

Try it on your clients' sites.

Connect your first sites today and see what SitePing finds on them.

  • Every Complete feature except backups
  • Up to 10 sites
  • No credit card needed to start
  • At the end you choose a plan or move to Free, and nothing is charged
Start the 30-day trial

Already have an account? Log in. Prefer to look at one site first? Free read-only audit.