WordPress released version 7.1.5 on November 18, 2026, to address 20 security issues in WordPress Core. The update fixes a flaw that could allow someone without an account to run code on a vulnerable server, two SQL injection flaws, and a weakness that could let an administrator of one site take over a WordPress Multisite network. WordPress recommends updating immediately.
Security researcher Logan Homolka reported the flaw in the Template Part block, which WordPress uses for shared layout elements such as headers and footers.
The flaw lets an unauthenticated attacker gain permissions they should not have and could lead to remote code execution (RCE). The announcement does not report attacks exploiting it or identify which site configurations could allow code execution.
The Template Part flaw is separate from the update-process weakness covered in our WordPress 7.1.4 security release report. The new release also fixes a distinct Multisite issue, reported by Yuval Miller, that could let a site Administrator take over a Super Admin account. That distinction matters because a Super Admin can manage the entire network, not just one site.
SQL Injection, XSS, and Data Exposure
Christiaan Swiers reported SQL injection in WP_Meta_Query, which builds database queries based on metadata. WordPress security team member Rudy Faile reported the second flaw, which affects front-page previews in the Customizer. SQL injection can change how a database interprets a query. The two flaws are separate from the export-related issue fixed in WordPress 7.1.3.
Several fixes address cross-site scripting (XSS), which can let an attacker run a script in another user’s browser. One stored XSS flaw affects comments and does not require an account.
Other fixes cover the legacy media library, embeds, and the block editor. The update also closes a data leak that exposed private taxonomy terms, such as categories or tags, through REST API search without a login.
The official WordPress release announcement also lists a denial-of-service flaw involving XML-RPC pingbacks and a permissions bypass in comment editing. The 20 entries include two preventive changes: stricter checks for JSON content types and removal of an Imgur embed option whose provider was already gone.
How to Update WordPress
Open Dashboard → Updates → Update Now, then confirm the installed version. Sites with automatic background updates can receive the patch without manual action, but administrators should still verify that it installed.
For older deployments, the WordPress 7.1.5 documentation lists patched versions by branch, including 7.0.9, 6.9.12, and 4.7.40. WordPress 4.6 and earlier no longer receive security updates.
Patches for older branches give administrators a way to close these flaws if they cannot move to 7.1.5 right away, but WordPress says only the latest version is actively supported. WordPress 7.2 Release Candidate 2 also contains the applicable fixes.
The final 7.2 release is planned for December 8, but site owners should install the available security update now rather than wait.
What Are Leading Organizations Doing About AI and Cyber Risks? Find Out. View Details!

