---
title: Tip: once a Drupal site is installed, the installer shouldn't be reachable and settings.php shouldn't be writable | ctxsec
url: https://ctxsec.com/items/tip-lock-down-drupal-install-php-and-read-only-settings-php-after-install
description: "SA-CORE-2026-017 abuses Drupal's own installer, and Drupal says some exploit paths fail when the web server can't write settings.php. Both are cheap hardening steps that also blunt future installer bugs."
status: "guide (based on Drupal SA-CORE-2026-017 and Drupal's installer guidance, Nov 2026)"
published: 2026-11-20
---

> SA-CORE-2026-017 abuses Drupal's own installer, and Drupal says some exploit paths fail when the web server can't write settings.php. Both are cheap hardening steps that also blunt future installer bugs.

[← Tips & Guides](/tips) · [markdown](/items/tip-lock-down-drupal-install-php-and-read-only-settings-php-after-install.md)

guide (based on Drupal SA-CORE-2026-017 and Drupal's installer guidance, Nov 2026)

2026-11-20 7:42 AM ET

### Tip: once a Drupal site is installed, the installer shouldn't be reachable and settings.php shouldn't be writable

- **Block the installer** at the web server or reverse proxy (deny `/core/install.php`) after setup, per Drupal's 'securing the installer' guidance.
- **Permissions:** `settings.php` and its directory owned by a deploy user and read-only to the web server (e.g. 444/555).
- **Check fleets** for staging and forgotten sites, which are the ones most likely to be left on old branches.

Sources: [Drupal SA-CORE-2026-017: Drupal core, Critical, Remote code execution, CVE-2026-132165 (Nov 18, 2026)](https://www.drupal.org/sa-core-2026-017) · [Drupal.org: Securing the installer (install.php)](https://www.drupal.org/docs/administering-a-drupal-site/security-in-drupal/securing-the-installer-installphp)
