Drupal Advisory Unleashes a Torrent of Attacks
Users only had 7 hours to update before the intrusions started.
On October 15, the Drupal security team announced an SQL injection vulnerability affecting Drupal 7 websites. A patch was quickly provided, and users were urged to upgrade their Drupal systems to Version 7.32. In a recent update to the original post, the team says that multiple attacks appeared “… in the wild following the release of this security advisory.” The extreme efficiency with which the vulnerability was turned into a real-world attack means that, according to Drupal, any site that wasn't patched within 7 hours of the original October 15 announcement should be considered compromised.
If a system was breached before the patch was applied, an update to the system doesn't help. In fact, it appears that an unexpectedly updated system is sometimes evidence of an attack. Intruders, it seems, are eager to update the system to Drupal 7.32 once they gain entry to prevent other intruders from slipping in also.
Ironically, the attack exploits a vulnerability in a Drupal API that is designed to help prevent SQL injection attacks.
If you did not get your Drupal site updated within 7 hours of the initial October 15 announcement, the Drupal team recommends the following steps:
- Take the website offline by replacing it with a static HTML page.
- Notify the server’s administrator, emphasizing that other sites or applications hosted on the same server might have been compromised via a backdoor installed by the initial attack.
- Consider obtaining a new server, or otherwise remove all the website’s files and database from the server. (Keep a copy safe for later analysis.)
- Restore the website (Drupal files, uploaded files, and database) from backups from before October 15, 2014.
- Update or patch the restored Drupal core code.
- Put the restored and patched/updated website back online.
- Manually redo any desired changes made to the website since the date of the restored backup.
- Audit anything merged from the compromised website, such as custom code, configuration, files or other artifacts, to confirm they are correct and have not been tampered with.
Subscribe to our Linux Newsletters
Find Linux and Open Source Jobs
Subscribe to our ADMIN Newsletters
Support Our Work
Linux Magazine content is made possible with support from readers like you. Please consider contributing when you’ve found an article to be beneficial.

News
-
Linux Mint 20 Reaches EOL
With Linux Mint 20 at its end of life, the time has arrived to upgrade to Linux Mint 22.
-
TuxCare Announces Support for AlmaLinux 9.2
Thanks to TuxCare, AlmaLinux 9.2 (and soon version 9.6) now enjoys years of ongoing patching and compliance.
-
Go-Based Botnet Attacking IoT Devices
Using an SSH credential brute-force attack, the Go-based PumaBot is exploiting IoT devices everywhere.
-
Plasma 6.5 Promises Better Memory Optimization
With the stable Plasma 6.4 on the horizon, KDE has a few new tricks up its sleeve for Plasma 6.5.
-
KaOS 2025.05 Officially Qt5 Free
If you're a fan of independent Linux distributions, the team behind KaOS is proud to announce the latest iteration that includes kernel 6.14 and KDE's Plasma 6.3.5.
-
Linux Kernel 6.15 Now Available
The latest Linux kernel is now available with several new features/improvements and the usual bug fixes.
-
Microsoft Makes Surprising WSL Announcement
In a move that might surprise some users, Microsoft has made Windows Subsystem for Linux open source.
-
Red Hat Releases RHEL 10 Early
Red Hat quietly rolled out the official release of RHEL 10.0 a bit early.
-
openSUSE Joins End of 10
openSUSE has decided to not only join the End of 10 movement but it also will no longer support the Deepin Desktop Environment.
-
New Version of Flatpak Released
Flatpak 1.16.1 is now available as the latest, stable version with various improvements.