← All articles

WordPress 7.1.5 Patches Critical Multisite Security Flaw

WordPress 7.1.5 Patches Critical Multisite Security Flaw

WordPress 7.1.5 fixes 19 security vulnerabilities, including a critical multisite privilege escalation and eight flaws that do not require an attacker to log in. Released on November 18, 2026, the security update also addresses cross-site scripting, SQL injection, information disclosure, authorization bypass, cross-site request forgery and denial of service. WordPress recommends updating immediately.

The highest-rated issue has a CVSS v3.1 score of 9.1. CVSS, the Common Vulnerability Scoring System, is a scale used to describe the potential severity of a security flaw. On multisite installations, an authenticated Administrator could abuse Customizer navigation-menu preview handling to take over a Super Administrator account. The flaw affects WordPress Core versions 4.3.0 through 7.1.4. It does not give an unauthenticated visitor Administrator access, and on a normal single-site installation an Administrator already has the highest ordinary role. WordPress 7.1.5 separates the security context used to validate those preview arguments.

Another major issue affects versions 5.9.0 through 7.1.4 and is rated 8.8, High. WordPress describes it as an unauthenticated privilege escalation through Template Part block attributes that could lead to remote code execution, meaning unwanted instructions could potentially be run on the site. Wordfence Intelligence classifies the issue as client-side cross-site request forgery, or CSRF, a trick that causes a logged-in user’s browser to send an unintended request. In the demonstrated path, an attacker prepared a crafted site-editor link and needed an Administrator to open it. The request created an attacker-chosen Administrator account on WordPress 7.1.4, while WordPress 7.1.5 issued no user-creation request. A low-privilege stored-input route and remote code execution were not demonstrated.

The release also fixes unauthenticated stored cross-site scripting through escaped shortcode attributes in comments, rated 7.2 and affecting versions 2.5.0 through 7.1.4. Cross-site scripting, or XSS, is malicious web script inserted into content and executed when someone views it. In the described route, an unauthenticated commenter submits encoded characters that pass comment filtering and are later decoded into HTML. The comment must be approved and rendered. On WordPress 5.0 and later, the affected content can pass through the Core Latest Comments block, with a crafted caption and video shortcode chain involving bundled MediaElement code.

Two other unauthenticated vulnerabilities have CVSS v3.1 scores of 7.5. One is SQL injection through nested WP_Meta_Query relation values. SQL injection is the insertion of unintended database instructions, potentially exposing sensitive information. The other is an XML-RPC denial-of-service flaw. XML-RPC is a WordPress remote communication interface, and denial of service means exhausting resources so normal requests are disrupted. An unauthenticated client could batch multiple pingback.ping calls in one XML-RPC system.multicall request, multiplying database and network work. The route requires XML-RPC to be reachable, and 7.1.5 limits each XML-RPC request to one pingback.

Wordfence tracks the remaining vulnerabilities by the access they require. Without authentication, the release fixes reflected XSS in the legacy media popup, XSS through the Interactivity API store namespace, private taxonomy-term disclosure through REST search, XSS through Openverse image metadata, and the issues already described involving comments, SQL injection, XML-RPC and Template Part attributes. REST, or Representational State Transfer, is a common way for software to exchange web requests.

Four flaws require Subscriber or Contributor access: private comment disclosure through XML-RPC, stored XSS through an oEmbed provider script, stored XSS through a Comment Date format value, and stored XSS through a filename during a media-to-File block transformation. Four require Author or Editor access: disclosure of a user’s current email address through REST comment editing, unauthorized movement of an approved comment to another user’s post, publication of a private editorial Note as a public comment, and account-existence disclosure across a multisite network through REST author assignment. Three require Administrator access: the critical multisite escalation, SQL injection through a Customizer front-page preview value, and stored XSS through Customizer previews.

The official WordPress announcement contains 20 security bullets, but Wordfence counts 19 vulnerabilities. Two bullets are described as hardening changes rather than vulnerabilities: correcting JSON media-type matching and removing an obsolete Imgur embed variation after the server-side provider was discontinued. One authorization-bypass bullet contains two separate issues involving comment editing, because one lets an Author move an approved comment and the other lets an Author turn a private editorial Note into a public comment. They have different attacker-controlled fields, impacts and affected version ranges. No CVE identifiers were listed in the public advisories at publication.

Most sites with automatic background updates enabled should begin receiving 7.1.5 automatically, but owners should confirm completion. In the WordPress dashboard, open Dashboard > Updates and verify that the site runs 7.1.5 or the corresponding fixed release for its branch. Backported fixes include 4.7.40, 4.8.35, 4.9.36, 5.0.32, 5.1.29, 5.2.31, 5.3.28, 5.4.26, 5.5.25, 5.6.24, 5.7.22, 5.8.20, 5.9.21, 6.0.19, 6.1.17, 6.2.16, 6.3.15, 6.4.15, 6.5.15, 6.6.12, 6.7.12, 6.8.13, 6.9.12, 7.0.9 and 7.1.5.

WordPress 4.6 and earlier no longer receive security updates. WordPress says only the latest release is actively supported, while older security backports are provided as a courtesy. Site owners should also review publishing and administrative access, remove unused accounts and keep each user at the lowest role needed. Wordfence recommends running a scan after updating to check Core file integrity and identify unexpected changes or malicious files for investigation. For site owners who want this managed, AEU Hosting provides managed WordPress hosting, secured end to end. Updating removes the vulnerable Core behavior, but the absence of one universal exploit path does not make this release optional.

Also available in: DeutschItalianoShqip