DKDKCISSP
VulnerabilitiesINCIDENT

Drupal Patches Critical Installer Flaw That Could Give Unauthenticated Attackers Control of Sites

Drupal has patched a critical vulnerability that could allow unauthenticated attackers to take control of sites using its installer.

DKCISSP News Desk19 Nov 2026, 8:03 pm2 min read
Drupal Patches Critical Installer Flaw That Could Give Unauthenticated Attackers Control of Sites
Image courtesy of The Hacker News. Original report

The Drupal Security Team has disclosed a critical vulnerability in Drupal core, tracked as CVE-2026-132165, which could permit unauthenticated attackers to leverage the built-in installer to take over sites or execute remote code. The flaw was rated 18 out of 25 on the project's risk scale and affects various versions of the platform.

Under specific conditions, the vulnerability allows attackers without login credentials to use the installer located at /core/install.php. This file remains on the site post-installation, and the default .htaccess rules do not block requests to it. As a result, site administrators must take action to secure it, as failure to do so could lead to site takeover or remote code execution.

The vulnerability is not widely exploited, with the security advisory noting that no attacks have been reported. However, it is marked as complex to exploit, and there is an existing proof-of-concept exploit. Some exploit paths are mitigated if the web server cannot modify permissions on the settings.php file, which adds a layer of protection for certain configurations.

The attack mechanism relies on the presence of the installer file, which is part of every Drupal installation. Attackers can potentially exploit this file to reinstall the site, which could lead to unauthorized access or control. Organizations using Drupal must ensure that this file is adequately protected to prevent unauthorized access, as it can serve as a gateway for attackers.

The vulnerability impacts all Drupal versions below 10.6.22, as well as specific 11.x releases. The Drupal Security Team has recommended that all affected sites update to the latest versions. Additionally, sites that cannot update immediately should follow the project's guidance to block access to the installer through various means, including web server configuration adjustments or removing the installer file altogether.

In the week of November 8, approximately 29 percent of the sites reporting usage data to drupal.org were running end-of-life versions, indicating a significant number of installations are potentially at risk.

The security team had previously warned site owners to prepare for an update, anticipating that exploits could be developed quickly.

While no attacks have yet been confirmed, the rapid development of exploits following vulnerability disclosures makes it critical for organizations to act swiftly. The security team also noted that the surge in vulnerability reports, attributed to AI tools, has strained their resources, leading to reduced security coverage for minor versions starting in 2027.

What security teams should do

  • Update to the latest supported version of Drupal to mitigate the vulnerability.
  • Implement measures to block access to the installer file as recommended by the security team.
MORE IN VULNERABILITIES

More cybersecurity reporting

Ruby Ships Fixes for 7 Flaws, Including Critical Ruby2Shell, Said to Hit Default Rails Apps Pre-Auth20 Nov 2026, 12:23 pmChina-Linked Hackers Exploited VMware ESX Zero-Day to Reduce Audit Trail Visibility20 Nov 2026, 12:05 pmNew Unpatched Windows 0-Day FastUnlock Lets Someone Holding a Locked PC Run Programs on It20 Nov 2026, 11:00 amCritical VMware vCenter Zero-Day Flaw Lets Network Attackers Bypass Authentication20 Nov 2026, 7:57 am