WordPress 7.1.5 fixes 18 vulnerabilities across core
WordPress 7.1.5 fixes 18 vulnerabilities among 20 security issues released on 18 November 2026. Patchstack added the 18 exploitable issues to its database, while the other two are hardening changes, meaning defensive code changes without an exploitable path. WordPress describes one issue as capable of remote code execution, where an attacker can make a system run commands, so site owners should update promptly through WordPress.org or the Dashboard.
The release follows WordPress 7.1.4, which arrived three weeks earlier with 17 fixes, including an unauthenticated core update race condition, meaning an attack that requires no login and exploits a timing window, tracked as CVE-2026-119977. Version 7.1.5 is broader. Five fixes come from an update to the Gutenberg package, which supplies block editor code, rather than from the core PHP backport. Those changes are in JavaScript and are not all represented in the official revised file list.
Two of the most serious issues begin with an unauthenticated visitor and reach an administrator’s browser. The Template Part block issue lets specially crafted block attributes influence REST paths, which are web addresses used by WordPress features to request or change data. The editor can send those requests with the logged-in user’s cookies and nonce, a temporary proof that a request came from an authorised WordPress session. WordPress says the issue can lead to remote code execution. Patchstack’s code review shows REST path injection, while the route to code execution depends on reaching plugin installation endpoints with an administrator’s own credentials. An attacker only needs to place the block markup in front of someone who can open it.
The release also addresses multisite privilege escalation through Customizer menu previews. Multisite is one WordPress installation serving multiple sites, and the issue could allow a site Administrator to become a Super Admin. The underlying problem involved the same hash being used for two different kinds of serialized data. Version 7.1.5 separates the data domains by adding a prefix to the serialized navigation menu arguments. On a single site, an administrator already has extensive control, but on multisite the distinction separates a site Administrator from a Super Admin.
Several fixes concern input that can reach database queries or browser code. An unauthenticated SQL injection issue affects nested relation values in WP_Meta_Query, the WordPress component that builds metadata database queries, when a caller passes request data into it. Another SQL injection issue affected the front page setting in Customizer changeset previews. WordPress now sanitizes previewed option values, just as saved values are sanitized, restricts the front page choice to page or posts, and uses $wpdb->prepare() around the affected query interpolation.
Cross site scripting, or XSS, means unwanted browser code is stored or inserted into a page and then runs for a visitor. Version 7.1.5 fixes stored XSS through shortcode attributes in comments, reflected XSS in the legacy media library popup, XSS through Openverse image metadata in the block editor, XSS through the store namespace in wp_interactivity_data_wp_context(), stored XSS through scripts in oEmbed provider responses, stored XSS in the Comment Date block’s format, stored XSS in media filenames when a media block becomes a File block, and stored XSS in Customizer previews.
Patchstack’s code analysis explains two of these paths in detail. Comment text is filtered against a 14 tag allowlist, but shortcode_parse_atts() previously decoded escaped characters such as \\x3c after that filtering had finished. A page containing the core Latest Comments block could then pass the comment excerpt through the_content, do_blocks and do_shortcode, allowing img_caption_shortcode() to print the result. The fix converts hexadecimal or octal escapes representing , double quotes or apostrophes into character references. The legacy media popup could also pass the complete $_GET array into wp(), allowing a rest_route value to dispatch the REST API inside an administrator page that had already declared an HTML content type. WordPress now returns early from rest_api_loaded() when WP_ADMIN is defined.
The Comment Date block issue is especially notable because it needs no visitor interaction. PHP date formats print unrecognised characters literally, and the block previously printed the format result without escaping it. The fix applies esc_html() to both linked and unlinked dates. The release also removes an Imgur embed variation from the block editor as a hardening change.
Other fixes expose or restrict information and permissions. WordPress closes an authorization bypass in administrator comment editing affecting Author and higher roles, prevents unauthenticated REST API searches from exposing private taxonomy terms, and stops the REST API comments endpoint from exposing user email addresses to Author and higher roles. It also fixes disclosure of post and template author assignments to Editor and higher roles, and disclosure of commenter email addresses and IP addresses through XML-RPC wp.getComments to Subscriber and higher roles. XML-RPC is an older method for sending WordPress requests over the web. A denial of service issue, which can make a site unavailable by exhausting resources, is also fixed in batched XML-RPC pingbacks.
The remaining browser and input fixes cover a reflected XSS path involving a victim who can upload files and click a link, Openverse image metadata inserted by an editor, untrusted namespaces passed by plugins or themes to wp_interactivity_data_wp_context(), and stored XSS through oEmbed provider responses from a Contributor or higher account. The release also hardens JSON media type matching against malformed regular expressions. The affected roles matter: six fixes concern what Contributor or higher users can reach, and WordPress advises site owners to audit those accounts. Multisite operators should review their Administrator lists as well.
The version 7.1.5 documentation page lists 18 revised files and says no package was revised. That list covers only the core PHP backport. The shipped release also changes wp-includes/blocks/comment-date.php, three bundled JavaScript packages and wp-includes/assets/script-loader-packages.php. Because the Gutenberg update carries five of the 20 fixes, including the Template Part issue, anyone comparing files to assess exposure should compare the packages too.
Backports were released on 18 November 2026 for every branch still receiving security fixes, through 4.7. Branches 4.6 and earlier no longer receive security updates. WordPress sites with automatic background updates will install the release automatically, while other site owners can use Dashboard, Updates. Patchstack reported that the published vulnerabilities had no CVE identifiers assigned at the time of publication.