WordPress 7.1.5, released on 18 November 2026, fixes about 20 security issues, among them an unauthenticated privilege escalation through Template Part block attributes that could lead to remote code execution, and two SQL injection flaws.
Drupal core fixes critical installer takeover flaw in SA-CORE-2026-017
EditorialBy TrustList Editorial
Drupal published SA-CORE-2026-017, a critical flaw that can let an attacker use install.php to reinstall a site and take it over, and SA-CORE-2026-018, a gadget chain, on 18 November 2026; releases 11.4.13, 11.3.22 and 10.6.22 came out that day.
- Cybersecurity
- Web Security
- Patch Management
- Web Development
About Drupal core fixes critical installer takeover flaw in SA-CORE-2026-017
Drupal core fixes critical installer takeover flaw in SA-CORE-2026-017
18 November 2026: The Drupal security team has published two core advisories. SA-CORE-2026-017 is rated critical: under specific conditions an attacker can use the installer to try to reinstall Drupal, which "can lead to a site takeover or remote code execution." SA-CORE-2026-018 is rated moderately critical and describes a gadget chain that becomes dangerous only alongside another flaw. New releases of drupal/core, 11.4.13, 11.3.22 and 10.6.22, appeared in Drupal's package registry alongside them.
Not yet independently verified. Advisory titles, risk scores, CVE numbers and the quoted descriptions come from the Drupal.org security listing and the core security feed of 18 November 2026, and the public service announcement of 16 November. The affected ranges and fixed versions are from the advisory text in the security feed and match the drupal/core releases tagged on 18 November; the individual advisory pages answered with a browser check and were not read. CVE.org had not yet published records for the two CVE numbers, so there is no CVSS score. We will update this when it can be confirmed, and remove this note.
The installer flaw
Drupal ships an install.php file that sets up a new site. The advisory, tracked as CVE-2026-132165, says that under specific conditions an attacker can use that file against an existing site. Drupal scores the risk at 18 out of 25. Its scoring marks the attack as complex and the affected configuration as uncommon, but the impact as total loss of confidentiality and integrity, and it records that proof-of-concept exploit code exists.
The security team had warned of the release two days earlier. Its public service announcement of 16 November said fixes for all supported branches would ship on 18 November between 17:00 and 21:00 UTC, that at least one flaw could be exploited by anonymous users, and that exploits "might be developed within hours or days". Sites covered by the Drupal Steward programme are protected against the known attack paths, according to the announcement, but updating remains the fix.
The pattern is familiar: TYPO3 fixed a similar installer takeover flaw on 17 November, and exposed installer files are an easy thing for attackers to look for.
The gadget chain
SA-CORE-2026-018, CVE-2026-132166, scores 14 out of 25. The advisory says Drupal core contains a chain of methods that could be exploited when an insecure deserialization vulnerability exists elsewhere on the site, for example in a contributed module, and that "this issue is not directly exploitable." Fixing it removes a building block that turns other bugs into code execution.
What site owners should do
Update drupal/core to the release for your branch: 11.4.13 for 11.4, 11.3.22 for 11.3 and 10.6.22 for 10.6, as tagged on 18 November. Branches 11.2 and older, 10.5 and older, and Drupal 8 and 9 are end of life and get no fix. With Composer, run composer update for drupal/core and its recommended packages, then run database updates and clear caches.
The advisory says some attack paths are blocked if the web server cannot write to settings.php or change its permissions, and it recommends securing the installer after installation. Whatever your version, make sure install.php cannot be reached from the internet on a live site. Blocking the core/install.php path at the web server or load balancer is a simple safeguard against the critical flaw and any repeat of it. Check that settings.php is read-only and that the database credentials in it cannot be overwritten by the web server user.
Sites on an end-of-life branch should move to a supported one or check with their extended support vendor. Agencies running many sites should prioritise those on shared or older hosting, where installer files are most often left exposed.
Sources
- Drupal.org: Security advisories, 18 November 2026
- Drupal.org: Security advisories for Drupal core (feed), 18 November 2026
- Packagist: drupal/core releases, 18 November 2026
Categories & features
- Cybersecurity
- Web Security
- Patch Management
- Web Development
TrustList Weekly
The week in software and IT, in one email
The news that matters to buyers, new rankings and our own research. Every Thursday, free, and easy to leave.
You may be interested in
FoxIO found seven of ten HTTP/3 stacks open to header amplification. quic-go, Cloudflare quiche, lsquic and Wireshark are fixed; Bun, the h3 crate and aioquic are not, and a proof of concept is public.
CVE-2026-114509 lets an attacker with no token log in as an existing user on apps using TokenGuard with MySQL or MariaDB. Upgrade to 13.29.0 or 12.68.0; a proof of concept is public.
PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35 close CVE-2026-109618 and CVE-2026-109619. Every PHP install serving web requests is at risk, mod_php most of all, and PHP 8.1 and older get no official fix.
Nine advisories published on 5 October cover four high-severity code execution paths through the Twig sandbox; Canada's Cyber Centre urged updates on 20 October. The fixes have been out since 1 September.
SA-CORE-2026-014 scores 19 out of 25. Sites on 11.2 or 10.5 and older have no patch; uninstalling the Field UI module blocks the flaw until an upgrade is possible.
Google announced the removal a year ago; the XSLTEnabled enterprise policy and an origin trial keep it working only until Chrome 176, due on 17 August 2027.
Edge 159 disables the XSLTProcessor API and XSL stylesheet instructions by default. A temporary XSLTEnabled policy buys time until Edge 176 in summer 2027.
More on TrustList
Everything here links back to the same verified catalogue. Pick your next stop.
- More CybersecurityThe ranking for this subject
- CompaniesAgencies, consultancies and IT service providers, ranked by verified reviews.
- ProductsSoftware and SaaS with pricing, features, integrations and alternatives.
- AwardsAnnual recognition decided by verified reviews and an independent jury.
- LaunchesNew products and releases, voted up by the community every day.
- AI ModelsBenchmark scores and community ratings for every major model.
- RequestsBuyers describe what they need; vendors respond directly.
- PeopleReviewers, authors and makers with public profiles.
- ComparePut up to four listings side by side before you shortlist.