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.
WordPress 7.1.5 security release fixes privilege escalation and SQL injection flaws
EditorialBy TrustList Editorial
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.
- Cybersecurity
- Web Security
- Patch Management
- Web Development
About WordPress 7.1.5 security release fixes privilege escalation and SQL injection flaws
WordPress 7.1.5 security release fixes privilege escalation and SQL injection flaws
18 November 2026: WordPress 7.1.5 is a security release, and the project recommends that sites update immediately. The release post lists about 20 fixes. The most serious is an unauthenticated privilege escalation through Template Part block attributes that, according to the post, could lead to remote code execution. Sites that allow automatic background updates will receive it without action.
Not yet independently verified. The list of fixes, the backport statement and the release date come from the WordPress.org release post of 18 November 2026, read on 19 November. The post gives no CVE numbers or severity scores, and the count of about 20 fixes is ours, from the list in the post. Backports to older branches were still in progress when we read it. We found no report of these flaws being exploited. We will update this when it can be confirmed, and remove this note.
The fixes that matter most
Beyond the Template Part flaw, the list includes two SQL injection issues: one in WP_Meta_Query through nested relation values, and one through the front page setting in Customizer changeset previews. On multisite networks, a flaw in Customizer menu previews let a site Administrator take over a Super Admin account, which matters to anyone who hands site administration to clients or departments while keeping network control.
Three more flaws need no login at all: stored cross-site scripting through shortcode attributes in comments, a denial of service through batched XML-RPC pingbacks, and disclosure of private taxonomy terms through the REST API search endpoint. A reflected cross-site scripting bug in the legacy media library popup is also fixed.
The rest require an account. Users with Author rights or higher could read other users' email addresses through the REST API comments endpoint and bypass authorisation when editing comments, and Subscriber accounts could read comment data through the XML-RPC wp.getComments method. Several cross-site scripting issues open to contributors and administrators are fixed in the block editor, Customizer previews and the Comment Date block.
Backports and other changes
The fixes are being backported to every branch still eligible for security fixes, which currently reaches back to 4.7. The post says those backports "will ship as they become ready", so a site pinned to an old branch may wait longer than one on 7.1. WordPress also stresses that only the most recent version is actively supported.
The release removes 1024-bit certificates from the bundled root certificate store, a change applied to 6.9.12 and earlier as well. WordPress 7.2 is planned for 8 December, and its second release candidate came out alongside this update.
The post does not give CVE numbers or severity scores. It follows 7.1.4, which fixed a race condition in the update process that had been exploited.
What site owners and agencies should do
Check that every site has moved to 7.1.5, or to the patched release of its branch once that ships. Automatic updates can be switched off by hosts, management plugins or a constant in wp-config.php, so confirm the version on the dashboard or through WP-CLI rather than assuming. Agencies with many installs should use their management tool to list sites still on 7.1.4 or older.
Multisite operators should treat the Super Admin flaw as urgent and review recently created administrator accounts. If XML-RPC is not needed, blocking xmlrpc.php at the web server also closes the pingback and wp.getComments paths. Review comments held for moderation for unusual shortcodes, and keep a recent backup before updating sites with heavily customised themes.
Sources
- WordPress.org News: WordPress 7.1.5 Security Release, 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.