Drupal 7 reached end of life on 5 January 2025, after several extensions. Since then the Drupal Security Team has published no Drupal 7 advisories and no Drupal 7 fixes. Yet a large number of Drupal 7 sites are still live, many of them in universities, charities and the public sector, where budgets and procurement make a quick move hard. If yours is one of them, this is what your options look like now.
What stopped in January 2025
- Security fixes for Drupal 7 core and contributed modules from the Drupal Security Team
- Compatibility updates, including fixes for newer PHP versions
- Security advisories, so new Drupal 7 vulnerabilities are no longer announced on drupal.org
The last point is the one people miss. It is not just that fixes stopped. Without advisories, you may not even hear about a new flaw in a module you rely on.
Option 1: Extended security support
The Drupal Association runs a programme that certifies commercial vendors to provide extended security support for Drupal 7. HeroDevs and Tag1 Consulting are the vendors it lists. Some hosting providers also bundle extended Drupal 7 cover for the sites they host, so check with yours. Extended support gives you security patches for core and covered contributed modules.
What it doesn't do is apply them. Someone still has to deploy each patch, test it, and look after everything around Drupal: PHP, the database, the server and any custom code. Extended support only covers the modules on the vendor's list, so check yours against it before you sign.
Option 2: Run it unsupported
Some organisations decide to keep Drupal 7 running with no patch source at all. It is a risk you can reduce but not remove, and it gets harder to defend every month. Supplier security questionnaires, insurers and audit frameworks increasingly ask whether your software is still supported by its vendor. If the honest answer is no, you need a documented plan and a date.
Hardening a Drupal 7 site you have to keep
- Put a web application firewall in front of the site and restrict access to
/userand the admin paths, ideally to known IP addresses - Remove modules, themes and user accounts nobody uses, since every one is more code without patches
- Keep PHP, the database and the server operating system on supported versions, even if Drupal itself is not
- Turn off features you no longer need, such as public registration, comments or file uploads
- Back up the site and test a restore, so a compromise is a bad day rather than a disaster
- Monitor file changes and admin logins, so you find out quickly if something does go wrong
Option 3: Plan the move
Extended support and hardening buy time. They don't fix the underlying problem, which is a platform with no future. Moving from Drupal 7 is a migration rather than an upgrade, because the code base changed completely in Drupal 8. It is usually also the right moment to rethink the content model and design. Our sister agency London Design Works plans Drupal 7 moves with a three-week Migration Blueprint, so you know the cost and timeline before committing.
Running Drupal 7 today?
We take over Drupal 7 sites, harden them and keep them running safely while a move to a supported version is planned with London Design Works.
See Drupal support and maintenance →