A Drupal Bug Could Let Anyone Hijack Your Site

TL;DR: A critical flaw in Drupal's installer lets unauthenticated attackers reinstall a site, potentially leading to a complete takeover or remote code execution. Drupal has released patches and says the vulnerable configuration is uncommon, but urges immediate updates.
Key facts
- Category
- Cybersecurity
- Impact
- Critical
- Published
- Source
- The Hacker News
Full summary
A critical Drupal installer flaw allows unauthenticated attackers to reinstall a site, leading to a complete takeover. Patches are available now.
The Drupal Security Team has issued patches for a critical vulnerability in its core software that could allow an attacker to take over a website completely. According to reports, the flaw allows a remote attacker, without any login credentials, to exploit the platform's installation script. By tricking an existing site into re-running the installer, an attacker could effectively overwrite its configuration and gain administrative control. This could lead to remote code execution (RCE), giving them the ability to run arbitrary commands on the server. While Drupal's team notes that the specific server configurations susceptible to this attack are considered "uncommon," the severity of a potential takeover prompted the immediate release of security updates for all supported versions of the popular content management system.
The vulnerability, identified as CVE-2024-29909, lies in how Drupal's installer handles requests on a site that is already up and running. Under normal circumstances, the installer should be inaccessible after the initial setup is complete. However, the flaw creates a condition where an attacker can bypass this protection and trigger the installation process again. This allows them to define a new site administrator and database connection, effectively hijacking the site. The success of the attack depends on specific, non-default server settings, but the nature of an unauthenticated RCE makes it a top-tier threat. It bypasses all standard layers of security, such as user passwords and permissions, by targeting the foundational setup logic of the application itself.
This incident fits into a broader pattern of high-impact vulnerabilities found in the installation and setup components of widely used web applications. Installer scripts are a tempting target for attackers because they are designed to have high-level permissions to write configuration files and create administrative accounts. Similar critical flaws have been discovered in the past in other major CMS platforms like WordPress and Joomla, often with devastating consequences. These events underscore the difficulty of securing every possible state of a complex application, especially edge cases that fall outside the normal operational flow. While Drupal's assessment that the vulnerable configuration is uncommon provides some reassurance, security researchers know that attackers excel at discovering and weaponizing such edge cases at scale across the internet.
For any organization using Drupal, the immediate and most crucial action is to apply the security patches provided by the project. The window between a vulnerability's disclosure and its widespread exploitation is often very short. Beyond this immediate fix, the incident serves as a powerful reminder of the importance of security hardening and adhering to deployment best practices. This includes ensuring that installer files are removed or made inaccessible after setup, implementing strict file permissions on the web server, and conducting regular security audits to identify misconfigurations. Teams should also have robust backup and incident response plans in place. In the coming days, security teams should monitor for any signs of scanning activity targeting this specific Drupal vulnerability, as proof-of-concept exploits are likely to emerge.
Why it matters
This is a critical, unauthenticated remote code execution (RCE) vulnerability in a major content management system. For developers and security teams, any flaw that allows a complete site takeover without needing credentials represents a worst-case scenario, requiring immediate patching to prevent exploitation.
Business impact
A compromised website can lead to significant business disruption, data breaches, and reputational damage. For companies using Drupal, this vulnerability poses a direct threat to their digital presence and customer trust. The cost of remediation after an attack far exceeds the effort of proactive patching.
⚡ Action needed
Update all supported Drupal core installations to the latest patched versions immediately. The vulnerability affects Drupal 9.5, 10.2, 10.3, and the upcoming 11.x branch.
Action checklist
- 1Identify all Drupal sites your organization manages.
- 2Determine which version of Drupal core each site is running.
- 3Review Drupal's security advisory SA-CORE-2024-004 for details.
- 4Apply the appropriate patched version for your Drupal branch.
- 5Verify the patch was successful and the site is functioning correctly.
- 6Confirm that installer files are not accessible on production servers.
Tags
Related on Notifire
Related stories
Primary source: The Hacker News