WordPress 7.1.5 fixes 20 security issues across core
WordPress 7.1.5 landed on 18 November 2026 as a security release containing twenty fixes. Patchstack added eighteen of them to its vulnerability database, while the other two are hardening changes with no exploitable path. The release affects every supported branch back to 4.7, and WordPress says two issues can begin with an unauthenticated visitor and reach an administrator’s browser. One of those can lead to remote code execution, meaning an attacker may make a system run commands of their choice.
The update follows WordPress 7.1.4, released three weeks earlier with seventeen fixes, including an unauthenticated core-update race condition tracked as CVE-2026-119977. WordPress 7.1.5 is broader than that release, and five of its fixes come from an updated Gutenberg package rather than the PHP code backport. Gutenberg is the block editor and its supporting code. Those changes include the Template Part issue, even though the official revised-file list does not mention the relevant JavaScript packages.
The highest-impact issue involves Template Part block attributes. A template part is identified by a key such as theme//slug. Before this release, WordPress built REST paths, which are web addresses used by the site interface to request data, by joining that key directly to a base address. Carefully chosen dot segments, an encoded slash, or a question mark or hash could redirect the request to another endpoint. The editor would send the request using the logged-in user’s cookies and security token. WordPress 7.1.5 adds a safety check called isSafeEntityKey() to several data and revision operations. The release note says the flaw can lead to remote code execution. Patchstack’s code review describes the direct problem as REST path injection, with the route to code execution relying on an administrator’s own plugin-installation permissions. It is considered unauthenticated because the attacker only needs to place the block markup before someone who can open it. Logan Homolka reported the issue.
Other fixes cover a wide range of permissions and content-handling problems. On multisite installations, Customizer menu previews could allow a site Administrator to become a Super Admin, the role controlling the entire network. Yuval Miller reported that issue. SQL injection, in which crafted input alters a database query, was fixed in WP_Meta_Query through nested relation values, reported by Christiaan Swiers, and through the front-page setting in Customizer changeset previews, reported by Rudy Faile and the WordPress Security Team. The latter was addressed by sanitising the preview value, restricting show_on_front to page or posts, and using $wpdb->prepare() for the affected query.
A batched XML-RPC pingback request could cause denial of service, making a site unavailable, according to Giovanni Cintolo’s report. XML-RPC is a method for sending commands to WordPress remotely. Stored cross-site scripting, or XSS, means unsafe browser code is saved and later shown to visitors. WordPress fixed stored XSS in shortcode attributes in comments when a page uses the Latest Comments block, reported by Rafie Muhammad and Awesome Motive; in Comment Date block formats, reported by Weston Ruter and Jeremy Felt with the WordPress Security Team; in media filenames converted from a media block to a File block, reported by CryptoFox; in Customizer previews, reported by Weston Ruter and the WordPress Security Team; and in scripts returned by oEmbed providers for Contributor or higher accounts, reported by vvh1te3zz.
Patchstack’s code review explains the comments flaw. Comment filtering allows no div or class attribute, but shortcode_parse_atts() decoded hexadecimal and octal escapes after that filtering had finished. A value such as \x3c could therefore become a less-than sign later. A page with the core Latest Comments block was also required, because the comment excerpt was processed inside the page content. WordPress 7.1.5 converts escapes that decode to angle brackets, quotation marks or apostrophes into character references instead.
The release also fixes reflected XSS in the legacy media-library popup, reported by Anthropic. A victim who can upload files had to click a link. The popup passed request data into wp(), allowing a rest_route value to dispatch the REST API from an administrator page that had already declared HTML output. WordPress now prevents that dispatch whenever WP_ADMIN is defined. XSS through Openverse image metadata in the block editor was reported by Shu Takahashi and Velcore Consulting. Another XSS issue affected wp_interactivity_data_wp_context() when a plugin or theme supplied an untrusted store namespace, reported by Juliette Reinders Folmer.
The Comment Date block issue required a Contributor or higher account and was unusual because it needed no visitor interaction. PHP date formats print unrecognised characters literally, and the block previously output the selected format without escaping it. WordPress now applies esc_html(), which converts unsafe HTML into harmless displayed text, to both linked and unlinked dates. Stored XSS through Customizer previews required an administrator. The preview path did not apply the same sanitisation used when an option was saved, so 7.1.5 sanitises preview values while temporarily suspending preview filters to avoid a loop.
The remaining vulnerability fixes include an author-level authorization bypass in admin comment editing, reported by Jesse McNeil; exposure of private taxonomy terms through the unauthenticated REST API search endpoint, reported by Anthropic; exposure of user email addresses through the REST API comments endpoint for Author or higher accounts, reported by Ben Bidner and the WordPress Security Team; disclosure of post and template author assignments through the REST API for Editor or higher accounts, reported by Jarda Snajdr and the WordPress Security Team; and disclosure of commenter email addresses and IP addresses through XML-RPC wp.getComments for Subscriber or higher accounts, reported by Jaewook Lee (grze0).
Two hardening changes complete the twenty fixes. WordPress tightened JSON media type matching after a malformed regular expression could broaden the match, in work reported by Mo Jangda and the WordPress Security Team. It also removed the block editor’s Imgur embed variation, following work reported by Zhengyu Liu, Jingcheng Yang and Gavin Zhong.
Patchstack warns that the documented file list is incomplete for exposure checking. The 7.1.5 documentation lists eighteen revised files and says no package was revised, but that describes only the 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. Those package changes carry five fixes, including the Template Part issue, so administrators comparing versions should examine the packages as well as the listed PHP files.