Security alert · Critical
Drupal core: critical installer flaw can allow site takeover without login
· 4 minutes read · Centoculus Security Team
Known since
Affected: Drupal core below 10.6.22, 11.0.0 to before 11.3.22, 11.4.0 to before 11.4.13 (end-of-life branches get no fix)
What happened
On 18 November 2026 the Drupal Security Team published security advisory SA-CORE-2026-017 for a critical vulnerability in Drupal core. It is rated 18 out of 25 on the project's risk scale. The flaw is in the built-in installer, the file /core/install.php. Under specific conditions an attacker without a login can use the installer to try to reinstall the site. This can lead to a site takeover or remote code execution.
The installer ships with every copy of Drupal core and stays on the site after installation. Drupal's default .htaccess rules do not block it, so each site has to block it on its own. The advisory rates exploitation as complex and notes that a proof-of-concept exploit exists. Some exploit paths are blocked if the web server cannot write to settings.php or change its permissions. The project rates the vulnerable configurations as uncommon.
No attacks have been reported so far. In an advance notice earlier in the week, however, the Drupal team warned that exploits might be developed within hours or days.
The same day, Drupal also fixed a second, moderately critical issue: a gadget chain. An attacker with administrator rights can only use it for remote code execution if the site also deserializes untrusted data because of another flaw. The same updates fix both issues.
Who is affected
- Drupal core releases below 10.6.22
- Drupal 11 releases from 11.0.0 up to, but not including, 11.3.22
- Drupal 11 releases from 11.4.0 up to, but not including, 11.4.13
These versions fix the flaw: 10.6.22, 11.3.22 and 11.4.13.
Drupal 11.2.x and earlier, 10.5.x and earlier, and Drupal 8 and 9 are end-of-life and will not get a fix. Sites on these branches must move to a supported branch. According to the Drupal team, sites protected by the paid Drupal Steward service are already protected against the known attack paths, but they should still update.
Sites that already run one of the fixed versions are not affected.
What to do now
- Back up the site's code,
settings.phpand the database. - Update Drupal core to the fixed release of your branch: 11.4.x to 11.4.13, 11.3.x to 11.3.22, 10.6.x to 10.6.22. On Composer-based sites, update
drupal/core-recommended(ordrupal/core) with its dependencies. Then run the database updates (for exampledrush updatedb) and rebuild the cache (drush cache:rebuild). - Sites on end-of-life branches (11.2.x or earlier, 10.5.x or earlier, Drupal 8 or 9) have no patch. Plan the upgrade to a supported branch now, and block the installer until then (step 4). The 11.3.x branch and Drupal 10 lose security coverage in December, so plan to move from those as well.
- Block the installer, even after updating. The Drupal team recommends this. Its guide "Securing the installer (install.php)" describes three options: a deny rule for
/core/install.phpin the web server configuration (Apache or nginx), a rule in the.htaccessfile in the web root, or deleting the file and using Composer scripts so it stays deleted after core updates. This is also the protection for sites that cannot update right away. - Make sure the web server user cannot write to
settings.php. This blocks some exploit paths. - Check the site afterwards: front page, login and the status report under Administration > Reports > Status report.
How to check whether you are affected
- Version: run
drush statusorcomposer show drupal/corein the project directory, or open the status report in the admin area. Compare the version with the fixed releases above. - Installer reachable:
curl -I https://example.com/core/install.phpshould return 403 or 404 once the installer is blocked or removed. - settings.php permissions: check with
ls -l web/sites/default/settings.php(the path depends on your setup). The file should not be writable by the web server user. - Signs of misuse: search the web server access logs for requests to
install.php, for examplegrep 'install.php' /var/log/nginx/access.log*or the matching Apache logs. Requests from unknown addresses, especially POST requests, deserve a closer look. Also check whethersettings.phphas changed recently and whether there are unknown administrator accounts. If a site has been reinstalled or shows unexplained changes, treat it as compromised.
Sources
If you run CMS or shop systems, also check
- WordPress plugin vulnerabilities: 8 plugins, including WPvivid Backup
- WordPress plugin vulnerabilities: 11 plugins, including Shortcodes for Phlox theme
- WordPress plugin vulnerabilities: 10 plugins including UpdraftPlus
- WordPress plugin vulnerabilities: 7 plugins, including Custom Twitter Feeds
- WordPress plugin vulnerabilities: 5 plugins including Optimole with 200,000 installs
- WordPress plugin vulnerabilities: 7 plugins including NextGEN Gallery
- WordPress plugin vulnerabilities: 12 plugins including WS Form LITE
- WordPress plugin vulnerabilities: 13 plugins including TranslatePress
- WordPress plugin vulnerabilities: 6 plugins including User Frontend
- WordPress plugin vulnerabilities: 5 plugins, including LiteSpeed Cache
Related posts
Alerts ·
VMware vCenter Server: critical authentication bypass fixed after zero-day attacks
Broadcom has fixed a critical authentication bypass in VMware vCenter Server (VMSA-2026-0009). Mandiant says it was used in zero-day attacks from early September 2026. vCenter 8.0, 9.0 and 9.1 are affected. ESX hosts are not.
Alerts ·
PHP fixes critical session flaw CVE-2026-115560 and six other code execution bugs
PHP 8.2.36, 8.3.37, 8.4.28 and 8.5.13 fix CVE-2026-115560 (CVSS 9.2), a session serializer mismatch that can lead to code execution. The same release fixes six more critical flaws, so every PHP server should be updated.
Alerts ·
Ruby: seven memory-safety flaws in regex and string handling, remote code execution possible
Ruby 4.0.10, 3.4.13 and 3.3.14 fix seven memory-safety flaws in the regex engine and in string case conversion. For five of them, the maintainers know of proofs of concept that run code. Ruby 3.2 and older get no fix.