The previous article inspected Drupal 11.4.11 and PHP 8.4.27 in DDEV. The Composer audit found no known vulnerability matches, but the administration screens showed several warnings, and a YAML file in the configuration synchronization directory could be retrieved anonymously.
This time I used those findings to update modules and review settings. The target remained my local DDEV environment. I kept Drupal 11.4.11 and PHP 8.4.27 in place while updating modules, removing unused features, and reviewing the location and protection of configuration files.
This article covers work performed on November 1, 2026 and the subsequent checks. Part 3 explains the removal of the Stable 9 dependency and the switch to an independent theme. The final results below describe the state after the full set of changes, including that theme work.
Prepare a way to restore the previous state
I first created a database snapshot and backed up the configuration files. The snapshot provides a way to restore the database to that point, including both articles and configuration stored in Drupal’s database.
Theme source code, PHP settings files, and web-server configuration are managed as files. Restoring the database alone would not restore those, so I preserved them separately. Since the work included uninstalling features and moving the synchronization directory, I made sure the earlier state was available before making changes.
Update Metatag and Token
After reviewing the administration notices, I updated Metatag and Token. Metatag handles page metadata, while Token provides placeholders for substituting values. I started with available updates that retained the features I used.
| Module | Before | After |
|---|---|---|
| Metatag | 2.2.3 | 2.2.5 |
| Token | 1.17.0 | 1.18.0 |
The dependency audit still found zero known vulnerability matches afterward. The presence of these update candidates did not itself establish a vulnerability. I recorded update availability separately from security-advisory matches.
Review usage before removing Contact and History
I had used Contact in the past, but no longer needed it in my current production and publishing workflow. I also decided that History was unnecessary for this site.
Contact provides contact forms. History tracks whether users have read content; it is different from revision history, which preserves versions of an article. I checked what the features actually did and how I used them, rather than deciding from their names.
Before uninstalling them, I checked for dependencies and data that needed to be retained. Within the scope inspected, nothing blocked removal. There were zero Contact messages, two form definitions, and two History rows.
Uninstalling is more than temporarily hiding a feature. It also removes the relevant configuration and data, so I prepared a recovery path first. I did not delete the user roles themselves.
This was a decision for my own environment. A site that accepts inquiries or uses these features needs to review its own usage before making the same changes.
Understand the HTML5 validation warning
The HTML5 validation warning concerned a change in how form validation is handled. Here, validation means checking such things as missing required values or incorrectly formatted input.
If the browser prevents submission first, Drupal’s validation and error display may never run. The official change record explains the implications for consistent error handling and accessibility.
Browser HTML5 validation is enabled by default in Drupal 11 and disabled in Drupal 12. To check Drupal’s own error handling, I explicitly set the following in Drupal 11 as well. Drupal’s official change record ↗
$settings['enable_html5_validation'] = FALSE;
This does not remove required-field validation itself. After the change, submitting an empty login form displayed Drupal’s required-field errors for the username and password.
That result does not mean every form was tested. Forms that change required-field conditions through JavaScript, for example, need separate checks when browser validation is disabled. What I actually verified was Drupal’s required-field handling on an empty login form, not the behavior of all custom or contributed-module forms.
The listing returned 403; an individual YAML file returned 200
One finding that stood out was a file in the configuration synchronization directory:
web/sites/default/files/sync/system.site.yml
Access to the synchronization directory returned 403. The .htaccess file in the same location was also unavailable. Requesting the existing system.site.yml directly, however, returned 200.
The SHA-256 hash of the response matched the local file, confirming that the file itself had been retrieved. This demonstrated anonymous retrieval of one file; I did not test every file in the directory or establish that all its information was exposed.
system.site.yml is an export of basic site settings. It also contained my local-use email address. I am not publishing its contents or the address itself.
Drupal’s active configuration normally lives in the database. The YAML here was an exported configuration file, not necessarily a file that updates automatically whenever the site’s basic settings change. This investigation did not establish when it was exported or which operation or tool created it.
File permissions are only part of the picture
At first, I considered whether I had made a permissions mistake somewhere. Unix file permissions alone, however, did not explain this situation.
The document root is the directory from which a web server serves public files. In this environment, that was web/, and the synchronization directory was inside it.
File permissions control which operating-system users can read and write a file. HTTP accessibility also depends on which paths the web server is configured to serve. If a readable file sits inside the public area, checking OS permissions alone does not establish that browser access is denied.
Here the configuration file was inside the public document root, and Nginx was not denying its retrieval over HTTP. Nginx does not apply Apache’s .htaccess access controls.
The synchronization location had also been supplied by DDEV’s generated settings as a fallback when no location was already configured. I am not treating this as proof of a vulnerability in DDEV as a whole or a newly discovered Drupal vulnerability. The finding concerns the actual combination of file placement and web-server configuration in this environment.
Move the synchronization directory outside the public area
I changed the layout to the following:
project/
├── config/
│ └── sync/ ← Configuration YAML
└── web/ ← Public document root
During the move, I checked file hashes and made sure no YAML files remained in the old location. I also added Nginx restrictions for the old synchronization URLs and direct access to PHP settings files. Drupal’s documentation describes placing the synchronization directory outside the public document root. Official instructions for changing the synchronization directory ↗
I updated the location Drupal uses, rather than just moving the files. I backed up the old exports outside the public area, then exported the active configuration after the changes to the new location. This avoided merely relocating the existing files while allowing the next export to recreate them at the old path.
The URL that previously returned 200 now returned 404. That means the file was not served in response to that request. I did not take this alone as evidence that every file on the site was protected; I checked the response for the changed path together with Drupal’s configured synchronization location.
Check again after restarting DDEV
I had previously noticed that changed permissions on settings files reverted after restarting DDEV.
Settings managed by DDEV can be generated or adjusted during startup. A permissions change made once while the project is running may not persist after a restart. I therefore kept project-specific settings separate rather than editing DDEV’s generated files directly.
On the Drupal side, a custom PHP settings file is loaded after DDEV’s generated settings. PHP runtime settings and Nginx access restrictions are also kept in separate configuration files. A DDEV post-start hook makes settings.php and the custom PHP settings file read-only after startup. A hook runs an action at a defined point in DDEV’s lifecycle.
After restarting, I confirmed that settings.php inside the container had mode 0444 and was not writable, and that the synchronization directory remained outside the public area. With Mutagen, permissions displayed on the host can differ from those inside the container, so I also checked the environment in which Drupal actually runs.
Restarting DDEV sometimes recreated the old synchronization directory itself. A reappearing directory is not the same as configuration YAML being restored there. I confirmed that the effective synchronization location remained outside the public area and that Nginx also denied the old path.
Check both warnings and actual responses
I also reviewed detailed error display and allowed hostnames. Addressing Stable 9 required resolving the theme dependency, so that work was done alongside the theme replacement described next.
Immediately after the module updates, the number of warning items fell from five to three, but anonymous retrieval of the YAML file still returned 200. Removing an update warning and fixing file exposure were separate outcomes.
After the settings changes described here and the theme dependency work in the next article, I refreshed the official update information. The final status report contained zero warnings and errors. I did not modify the report to hide warnings. The main final checks were as follows.
| Check | Result after the full set of changes |
|---|---|
| Drupal status report | Zero warnings and errors |
| Composer dependency audit | No known vulnerability matches in either the lock file or installed packages |
| PHP and extension requirements | All 22 checks successful |
| Settings files after restart | Mode 0444 inside the container; not writable by the CLI user used for the check |
| Configuration synchronization directory | Remained outside the public document root |
| Previously retrievable YAML URL | Changed from 200 to 404 |
| Anonymous access to administration pages and update scripts | 403 |
| Main pages | 200; rendering checked |
composer validate --strict still reported warnings because the core-related packages were pinned exactly to 11.4.11. I retained those constraints to fix the comparison conditions. These are separate from warnings and errors in Drupal’s status report; the result does not mean every tool was warning-free.
The number of administration warnings is one useful signal. Individual HTTP checks can reveal other issues, as the YAML file did here. For checks before publishing, I want to retain both the configuration values and the actual access results.
Follow-up: official-source comparison (November 4, 2026)
These notes were added after reviewing official sources on November 4. They are separate from the November 1–2 measurements; no Drupal environment was changed or retested.
Removing an unused feature differs from replacing a needed one
Contact and History were removed after checking their use and deciding they were unnecessary in this environment. Deprecation does not mean every site should uninstall them. The official extension lifecycle documentation ↗ also describes switching to contributed replacements through Composer.
When retaining functionality, review its replacement, compatible versions and dependencies. Do not uninstall an extension merely to change providers if its data must be retained. The removal decision, backups and restart results remain historical measurements. See the related User Guide annotation .
File exposure and configuration-import regressions are distinct
The anonymous YAML retrieval demonstrated here concerns file location and web-server configuration. Separately, the 11.3.8 release note ↗ records a data-loss regression when importing configuration on 11.3.6/11.3.7. Although both involve configuration, their causes and affected versions differ. The HTTP tests on 11.4.11 did not reproduce that regression.