top of page

The Builders’ Forgotten Door: How a Critical Drupal Flaw Could Let an Impostor Rebuild the Castle

hace 1 día
8 min de lectura

The castle had stood for years.

Its towers overlooked the surrounding kingdom. Its walls protected the inhabitants. Its guards inspected every entrance.

The king believed the fortress was secure.

But hidden behind one of its oldest corridors was a door that nobody had thought to remove.

It wasn’t a secret passage built by an enemy.

It wasn’t a tunnel dug beneath the walls.

It was the entrance once used by the castle’s own builders.

When the fortress was first constructed, that entrance had allowed the builders to establish its foundations, configure its defenses and prepare the building for its first inhabitants.

Once construction was complete, the door was supposed to become irrelevant.

But it remained.

And one day, an impostor discovered it.

He didn’t have the king’s permission.

He didn’t possess a guard’s credentials.

He wasn’t even a recognized visitor.

Yet under certain conditions, the forgotten entrance could allow him to initiate the construction process again.

This time, the castle already belonged to someone else.

The impostor wasn’t trying to break down the walls. He was trying to make the castle forget that it had already been built.

On November 18, 2026, the Drupal Security Team disclosed CVE-2026-132165, a critical vulnerability affecting Drupal Core.

The flaw involves the built-in installation mechanism and can, under specific conditions, allow an unauthenticated attacker to attempt to reinstall an existing Drupal website.

Successful exploitation could lead to complete site takeover or remote code execution.


Phase 1 — The Door the Builders Left Behind


When the castle was first constructed, its builders needed a special entrance.

Through that entrance, they could establish the building’s configuration and prepare it for use.

Drupal has an equivalent mechanism.

Every Drupal Core installation includes an installer located at:

/core/install.php

This file supports the initial installation of Drupal.

However, the installer remains present after the website has been deployed.

That is not automatically a vulnerability.

A correctly secured installation should prevent unauthorized users from abusing installation functionality.

But the Drupal Security Team identified circumstances in which the installer could be invoked against an existing website.

The default .htaccess configuration does not specifically block access to the installer.

Administrators therefore need to ensure that it is appropriately protected.

The builders had finished constructing the castle. But the door they used to begin construction was still accessible.


Phase 2 — The Impostor Finds the Forgotten Entrance


The impostor approached the castle without a uniform.

He had no identification.

He knew no passwords.

But the forgotten builders’ entrance was different from the main gate.

It had been designed for a time before the castle was fully operational.

And that difference created an opportunity.

CVE-2026-132165 can be exploited without authentication under specific conditions.

This means an attacker does not necessarily need an existing Drupal account to attempt exploitation.

The vulnerability is rated Critical, 18 out of 25, under Drupal’s security risk assessment.

Its classification also reflects important limitations:

  • Attack complexity is considered high.

  • Vulnerable deployment configurations are uncommon.

  • A proof-of-concept exploit exists.

  • No real-world exploitation was reported in the advisory.

These qualifications matter.

The vulnerability is serious, but it does not mean every Drupal installation can be taken over simply by visiting the installer.

The impostor had found a dangerous entrance. But whether it opened depended on how the castle had been secured.


Phase 3 — The Castle Is Told to Build Itself Again


The impostor’s plan was unusual.

Most invaders try to seize a castle by force.

They attack its gates, climb its walls or bribe its guards.

This intruder wanted something different.

He wanted to activate the mechanism responsible for constructing the fortress.

In Drupal, the vulnerable behavior can allow an attacker to attempt to reinstall an existing website through its installation functionality.

Under the necessary conditions, that operation can interfere with the site’s established configuration.

The potential consequences include:

Site takeover: The attacker may gain control over the affected Drupal installation.

Remote code execution: Certain exploitation paths may allow unauthorized code to execute on the server.

Both outcomes are severe.

A compromised website can expose sensitive information, disrupt services or provide a foothold for further malicious activity.

However, the precise outcome depends on the environment and whether the necessary exploitation conditions are satisfied.

The impostor didn’t need to convince the king to surrender. He wanted the castle’s own construction machinery to give him control.


Phase 4 — The Walls That Could Stop the Impostor


Not every castle was vulnerable.

Some had been constructed with stronger protections around the builders’ entrance.

Even if the impostor reached it, he could not alter the foundations.

Drupal’s advisory identifies an important defensive condition involving:

settings.php

This configuration file contains essential Drupal settings.

Some exploitation paths are mitigated when the web server cannot write to this file or change its permissions.

That is an important distinction between a properly hardened environment and one with unnecessarily permissive file access.

If the web server process cannot modify sensitive configuration files, certain attempts to abuse the installer become more difficult or impossible.

But file permissions alone should not be treated as a complete substitute for the security update.

The Drupal Security Team recommends both patching and securing the installer.

A forgotten door was dangerous. But a properly protected foundation could prevent the intruder from rebuilding the castle.


Phase 5 — An Artificial Intelligence Finds the Weakness


The discovery itself adds another dimension to the story.

The vulnerability was identified by Anthropic’s OSS Scanner, an automated vulnerability-discovery service.

Drupal’s advisory credits the finding as:

ANT-2026-GMRPK0BU

The scanner was designed to help identify security weaknesses in participating open-source projects.

This illustrates a constructive use of artificial intelligence in cybersecurity.

Automated analysis can help defenders identify vulnerabilities that might otherwise remain unnoticed.

In this case, the discovery gave Drupal’s maintainers an opportunity to develop and distribute fixes.

But the broader environment presents a challenge.

Automation can accelerate vulnerability discovery, while public disclosures and patches may also attract attention from attackers attempting to develop exploits.

Drupal warned administrators before releasing the fixes that exploitation methods could emerge quickly following disclosure.

A mechanical inspector discovered the forgotten door before an invading army was known to have used it.


Phase 6 — The Kingdom Receives an Urgent Warning


The Drupal Security Team issued an advance warning on November 16, 2026.

Administrators were advised to reserve time for important security updates.

Two days later, on November 18, the fixes became available.

The affected supported versions and corresponding updates are:

Drupal branch

Fixed version

Drupal 11.4.x

11.4.13

Drupal 11.3.x

11.3.22

Drupal 10.6.x

10.6.22

The affected ranges include Drupal releases earlier than 10.6.22, Drupal 11.0.0 through 11.3.21, and Drupal 11.4.0 through 11.4.12.

Older branches require particular attention.

Drupal 11.2.x and earlier, Drupal 10.5.x and earlier, and Drupal 8 and 9 no longer receive the relevant standard security coverage.

Organizations operating unsupported versions should plan a migration to a supported release rather than expecting a patch for their obsolete branch.

The kingdom had received the warning. Now every castle owner needed to reinforce the forgotten entrance.


Phase 7 — Closing the Builders’ Door


Updating Drupal is the primary remediation.

But the Drupal Security Team also recommends protecting the installer after the update.

There are several ways to accomplish this.

1. Block the installer at the web server.

Configure the server to deny unauthorized requests to /core/install.php.

2. Use appropriate .htaccess restrictions.

On compatible Apache configurations, administrators can use access-control rules to prevent requests from reaching the installer.

3. Remove the installer where appropriate.

Drupal documents an option for removing the installation file and ensuring it remains removed through Composer-based deployment scripts.

4. Protect configuration files.

Ensure the web server does not have unnecessary write access to settings.php or the ability to change its permissions.

5. Keep Drupal Core updated.

The installer restrictions provide defense in depth, but the supported security release remains essential.

These actions reduce the likelihood that installation functionality can be misused against an already deployed site.

The safest solution wasn’t merely to station another guard beside the old entrance. It was to make sure that entrance could no longer be used by outsiders.


Phase 8 — The Castle’s External Defenses


Some Drupal installations benefit from additional protection through Drupal Steward.

Drupal Steward provides a web application firewall service intended to protect participating sites against certain vulnerabilities.

According to Drupal’s advisory, the service already protects against some known attack vectors for CVE-2026-132165.

However, that protection is not comprehensive.

New exploitation techniques may emerge.

And a web application firewall does not necessarily eliminate the underlying vulnerable code.

For that reason, Drupal explicitly recommends upgrading even when Steward protection is active.

This is a fundamental principle of layered security.

A firewall may intercept known malicious requests.

File permissions may restrict what a compromised process can modify.

Access restrictions may prevent the installer from being reached.

And the security update addresses the vulnerability itself.

A castle is safest when its guards, gates and foundations all contribute to its defense.


Phase 9 — The Danger of Abandoned Castles


One of the most concerning aspects of the disclosure involves unsupported Drupal installations.

According to usage figures cited in the reporting, approximately 154,485 of 528,430 reporting sites, or about 29%, were running end-of-life Drupal branches during the week of November 8.

These figures represent sites reporting usage data to Drupal.org, not a complete census of every Drupal website.

Nevertheless, they illustrate the scale of legacy infrastructure.

Older installations can remain online for years.

They may support important services.

They may contain sensitive information.

And they may no longer receive standard security fixes.

A forgotten installer on an unsupported system creates a particularly difficult situation.

The organization cannot assume that its existing software branch will receive a permanent fix.

It may need to upgrade, migrate or introduce temporary protective controls while planning a supported deployment.

Drupal 11.3.x and Drupal 10 are also approaching the end of their security coverage in December 2026.

The oldest castles were not necessarily the weakest because of their age. They were vulnerable because nobody was maintaining their defenses anymore.


Phase 10 — The Defenders Inspect the Entire Fortress


Organizations responsible for Drupal installations should treat the disclosure as a reason to review both software versions and deployment configuration.

A practical response includes:

  1. Identify every Drupal installation, including staging and less-visible sites.

  2. Determine whether each site runs an affected or unsupported release.

  3. Upgrade supported installations to the relevant fixed version.

  4. Restrict public access to /core/install.php.

  5. Verify that sensitive configuration files have appropriate permissions.

  6. Review web server and application logs for suspicious installer requests.

  7. Validate site integrity and investigate unexplained configuration changes.

  8. Maintain reliable backups and test restoration procedures.

  9. Check security support dates for all deployed Drupal branches.

  10. Continue monitoring Drupal’s official advisories for additional guidance.

Importantly, the published advisory did not report confirmed attacks exploiting CVE-2026-132165.

The existence of a proof of concept should therefore be understood as evidence of exploit feasibility, not proof that widespread compromises have occurred.

The defenders had been given time to secure the castle. The question was whether they would close the forgotten door before someone tried to use it.


The Final Scene — The Door That Should Have Been Sealed


The impostor stood outside the castle.

He could see the guards on the walls.

He could hear the soldiers patrolling the courtyard.

And he knew the king believed the fortress was secure.

But the impostor wasn’t interested in fighting the soldiers.

He was studying an old entrance.

A door that had been installed when the castle was nothing more than a construction site.

A door that should have become inaccessible once the first king took the throne.

For years, nobody had paid attention to it.

The builders had moved on.

The inhabitants had settled inside.

The castle had grown.

But the old entrance remained.

Under the right conditions, it could give an outsider access to the machinery that controlled how the fortress was established.

The discovery of CVE-2026-132165 exposed a comparable weakness in Drupal Core.

A mechanism intended to install a website could potentially be abused against one that was already operational.

Drupal responded with security updates and guidance for securing the installer.

No exploitation in the wild had been reported.

But the lesson was unmistakable.

A system’s installation mechanisms can remain security-sensitive long after deployment.

And leaving those mechanisms accessible can create risks that ordinary perimeter defenses were never designed to address.

The king ordered the old door sealed.

The builders’ tools were locked away.

The foundations were reinforced.

And the guards finally understood what had nearly made their defenses irrelevant.

The castle was never supposed to be built twice.

But the impostor had discovered that the door used to build it could also become the door used to steal it.


 
 
 

Comentarios


bottom of page