The Daily Byte
Breaking
Welcome to The Daily Byte — real stories from across Pakistan.
Saturday, 21 November 2026 · Pakistan

The Daily Byte

Stories from Pakistan that deserve to be heard

WordPress 7.1.5 fixes 20 security flaws

By The Daily Byte ·21 Nov 2026 ·4 min read
A laptop displaying the WordPress.org homepage

WordPress has released version 7.1.5, a security update that fixes 20 issues in the software behind a large share of the world's websites. The release went out on 18 November 2026, and WordPress says site owners should update immediately. Because it is a short-cycle security release, the same fixes have been backported to older branches, reaching back to version 4.7.

The most serious issue sits in the Template Part block. An unauthenticated attacker can craft a link to the block editor that, when a signed-in administrator opens it, makes the administrator's own browser create a new administrator account for the attacker. From there, the attacker can install a plugin and run whatever code they want. A user with the Author role or above can plant the same malicious settings inside a post. The flaw, reported by Logan Homolka, affects WordPress 5.9 and later. Cloudflare's briefing on the release, reviewed on 19 November, notes that five of the 19 published security advisories are rated high, and that no CVE numbers had been assigned to these issues yet.

Four flaws need no login at all

Three further flaws can be used by a visitor with no account. One is an unauthenticated stored cross-site scripting flaw in shortcode attributes inside comments, reported by Rafie Muhammad of Awesome Motive. It can inject script into pages where a Comments or Latest Comments block is used. A second is an unauthenticated denial of service through batched XML-RPC pingbacks, reported by Giovanni Cintolo, which can tie up the server's PHP workers. The third is an unauthenticated information disclosure flaw that exposes private taxonomy terms through the REST API search endpoint, reported by Anthropic.

Site owners should not assume these flaws are harmless because they look narrow. Stored cross-site scripting lets an attacker run script in the browsers of people who visit the affected pages, and a denial of service flaw can take a small site offline with little effort from the attacker.

Multisite takeover, SQL injection and scripting flaws

On multisite installations, a site administrator can take over a Super Admin account through Customizer menu previews, an issue reported by Yuval Miller. Two SQL injection flaws were also fixed: one in WP_Meta_Query through nested relation values, reported by Christiaan Swiers, and one through the front page setting in Customizer changeset previews, reported by Rudy Faile of the WordPress Security Team.

The rest of the release is a cluster of cross-site scripting and information disclosure fixes. They include a reflected scripting flaw in the legacy media library popup, reported by Anthropic; scripting flaws in the block editor through Openverse image metadata and through media filenames when converting a media block to a File block; scripting flaws for Contributor-level users in the Comment Date block and in oEmbed provider responses; and an administrator-level stored scripting flaw in Customizer previews. Information disclosure fixes cover user email addresses exposed through the REST API comments endpoint, post and template author assignment in the REST API, and comment data exposed through XML-RPC. Two hardening changes are also included: a corrected regular expression for JSON media type matching, and the removal of the block editor's Imgur embed variation, whose server-side provider no longer exists.

No attacks reported yet, but check your version

As of 19 November, no source had reported exploitation of these issues, and none of them appears in CISA's catalogue of exploited vulnerabilities. That can change quickly. A different WordPress core flaw fixed earlier in November, CVE-2026-119977, was listed by CISA as exploited, which is a reminder that WordPress flaws attract attention fast once fixes are public.

The fixed versions are 7.1.5 for the 7.1 branch, 7.0.9 for 7.0, and 6.9.12 for 6.9, with matching November 18 releases for older branches back to 4.7. WordPress 4.6 and earlier receive no security updates and should be upgraded. Sites with automatic background updates should already have the fix, but owners should check rather than assume: open Dashboard, then Updates, and confirm the installed version. Until a site is updated, administrators should not open editor links they were not expecting, and after updating it is worth checking the Users list for administrator accounts nobody recognises. WordPress says the next major release, version 7.2, is planned for 8 December, and that its second release candidate already contains these fixes.