WordPress 7.1.5 Blocks Critical Multisite Account Takeover
WordPress 7.1.5 fixes 19 security vulnerabilities in WordPress Core, including a Critical multisite privilege escalation and an unauthenticated flaw that WordPress says could lead to remote code execution. Released on November 18, 2026, the 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, a Critical rating used to describe the potential severity of a vulnerability. It affects WordPress 4.3.0 through 7.1.4 on multisite installations. An authenticated site Administrator can abuse Customizer navigation menu preview handling to cross the boundary separating site administration from network administration and take over a Super Administrator account. The attack requires an Administrator account and multisite, and does not give an unauthenticated visitor administrative access. WordPress 7.1.5 separates the security context used to validate the preview arguments.
Another major issue affects versions 5.9.0 through 7.1.4 and has a CVSS v3.1 score of 8.8, rated High. WordPress describes it as an unauthenticated privilege escalation through Template Part block attributes that could lead to remote code execution. Wordfence Intelligence classifies the tested path as client side cross site request forgery, a trick that causes a logged in user’s browser to send an unwanted request, leading to Administrator account creation. An attacker prepares a crafted site editor link, but an Administrator must open it. In testing, the link created an attacker chosen Administrator on 7.1.4 whose credentials worked in a separate login. On 7.1.5, no user creation request was issued. A low privilege stored input path and remote code execution were not demonstrated.
WordPress 7.1.5 also fixes unauthenticated stored cross site scripting through escaped shortcode attributes in comments. Cross site scripting, often abbreviated XSS, means that harmful browser code is inserted into content and runs when someone views it. The issue affects versions 2.5.0 through 7.1.4 and is rated 7.2 High. An unauthenticated commenter can submit specially encoded characters that pass comment filtering and are later decoded into HTML. On WordPress 5.0 and later, an approved comment shown through the Core Latest Comments block can reach the normal shortcode processing path. A crafted caption and video shortcode chain can cause bundled MediaElement code to reconstruct and execute an image event handler from a track label. The comment must be approved and rendered. Earlier versions require another integration that processes comment content as shortcodes.
Two other unauthenticated issues are rated 7.5 High. A SQL injection flaw in nested WP_Meta_Query relation values can let an attacker alter database queries and access sensitive information. SQL injection is the insertion of unexpected database instructions through an application input. A separate XML RPC denial of service issue lets unauthenticated clients batch multiple pingback.ping calls inside one system.multicall request. Each pingback can create database and network work, multiplying server load when XML RPC is reachable. WordPress 7.1.5 limits each XML RPC request to one pingback.
Wordfence counts eight vulnerabilities that need no attacker authentication. These are the Template Part privilege escalation, the comment shortcode XSS, legacy media popup reflected XSS, Interactivity API store namespace XSS, Openverse image metadata XSS, the nested WP_Meta_Query SQL injection, private taxonomy term disclosure through REST search, and batched XML RPC pingback denial of service. The remaining issues require different levels of access or conditions. Subscriber or Contributor access is enough for private comment disclosure through XML RPC and three stored XSS issues involving oEmbed provider scripts, Comment Date format values and a filename used during a media block to File block transformation. Author access can expose a user’s email address through REST comment editing, move an approved comment to another user’s post, or publish a private editorial Note as a public comment. Editor access can expose whether accounts exist across a multisite network through REST author assignment.
Three issues require Administrator access: the multisite Super Administrator escalation, SQL injection through a crafted Customizer front page preview value, and stored XSS through Customizer previews. The 19 records also include the two reflected or namespace related XSS issues and private taxonomy disclosure listed above. CVSS v4.0 scores are also included in the Wordfence records, because the newer scoring standard models impact differently. No CVE identifiers were listed in the public advisories at publication time.
WordPress’s announcement contains 20 security bullets. Wordfence treats two as hardening changes rather than separate vulnerabilities: a correction to JSON media type matching, where a malformed regular expression could match a wider range of media types than intended, and removal of an obsolete Imgur block editor variation after its server side provider was discontinued. One authorization bypass bullet contains two separate flaws, involving comment movement and publication of a private Note, so Wordfence tracks 19 vulnerability records in total.
Most sites with automatic background updates enabled should begin receiving WordPress 7.1.5 automatically, but owners should confirm completion by opening Dashboard > Updates and checking for WordPress 7.1.5 or the corresponding fixed release for the site’s 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, and WordPress says only the latest release is actively supported, with older backports provided as a courtesy.
After updating, owners should review publishing and administrative access, remove unused accounts and give each user only the lowest role needed. Wordfence recommends a scan to verify Core file integrity and identify unexpected changes or malicious files for investigation. AEU Hosting offers managed WordPress hosting, secured end to end, which is directly relevant to sites that need a security focused hosting arrangement around their WordPress installation. The absence of one universal attack path does not make this release optional: site owners should update every eligible site and confirm that the fix is active.