WordPress 7.1.5 security release displayed on a laptop as a site administrator reviews an update WordPress 7.1.5 security release displayed on a laptop as a site administrator reviews an update

WordPress 7.1.5 Security Release Fixes 18 Vulnerabilities

WordPress 7.1.5 arrived on November 18 with 20 security fixes, including 18 vulnerabilities and two hardening changes. Here are the notable issues and what site owners should check.

WordPress 7.1.5 landed on November 18, 2026, with 20 security fixes. In its release analysis, Patchstack says 18 fixes address vulnerabilities and two are hardening changes. Site owners can use the release details to identify the risks relevant to their setup and check that their WordPress branch has a patched version.

WordPress 7.1.5 addresses issues ranging from unauthenticated SQL injection and cross-site scripting to privilege escalation on multisite installations. Patchstack says one vulnerability can lead to remote code execution if an editor opens attacker-controlled content. The release also includes fixes shipped through a Gutenberg package update, a detail that matters when reviewing the changes.

What the WordPress 7.1.5 security release fixes

The 20 fixes cover several parts of WordPress, including the block editor, Customizer, REST API, XML-RPC and comment rendering. Patchstack lists unauthenticated issues as well as flaws that require an account with a particular role, such as Contributor, Author or Administrator.

Among the most serious items in the report are an unauthenticated privilege-escalation path involving Template Part block attributes, a multisite privilege-escalation issue, and SQL injection through nested relation values in WP_Meta_Query. The Template Part issue requires an editor to open the affected content; Patchstack says the release notes describe its potential to lead to remote code execution.

The release also fixes an unauthenticated denial-of-service issue involving batched XML-RPC pingbacks, an unauthenticated exposure of private taxonomy terms through REST API search, and several cross-site scripting vulnerabilities. Some XSS issues need a user with a particular role or an editor to interact with content; Patchstack says the Comment Date block issue can render its injected markup to visitors when a page loads.

Several fixes come from a Gutenberg package update

One detail is easy to miss if you review only the documented list of changed files. Patchstack says five fixes came from a Gutenberg package bump, rather than the core PHP backport. Those changes include the Template Part issue and live in JavaScript packages.

Patchstack reports that the WordPress 7.1.5 documentation page lists 18 revised files and says no package was revised. Its analysis says the shipped release also changes the Comment Date block file, three bundled JavaScript packages and the script-loader package file. The practical takeaway for anyone reviewing code changes is to include package changes in the review, rather than relying on the documented file list alone.

The two remaining fixes are described as hardening changes, not vulnerabilities with an exploitable path. One changes regular-expression handling for JSON media types; the other removes the block editor’s Imgur embed variation.

Who should pay closest attention

Sites with user accounts should review who has Contributor-level access or higher. Patchstack’s report includes fixes affecting Contributor, Author and Editor roles, as well as issues involving administrators. The exact requirements vary by vulnerability, so a lower-privileged account is not required for every issue.

Multisite administrators should check site-level Administrator access in particular. Patchstack describes a vulnerability that could let a site Administrator escalate to Super Admin through Customizer menu previews. That finding is separate from the Template Part issue and has its own access conditions.

Sites that use the Latest Comments block should also note Patchstack’s explanation of the shortcode-related issue. The vulnerable path depended on a page displaying comment excerpts through that block. The release changes how certain escaped characters are decoded in shortcode attributes.

Update availability and older branches

Patchstack says WordPress 7.1.5 is available through Dashboard updates or from WordPress.org. It also reports that patched releases were issued for every branch still receiving security fixes, back to WordPress 4.7. Branches 4.6 and earlier no longer receive security updates.

If a site does not run the current branch, check the release information for the branch it uses and apply its corresponding patched version. Do not assume that installing a different branch’s release number is the right update. Patchstack says sites with automatic background updates will receive the update automatically, but site owners should verify the installed version.

Patchstack reported that no CVE identifiers had been assigned to the newly published vulnerabilities when its article appeared on November 18. That is a point-in-time detail from the report, not a reason to delay applying the available fixes.

Frequently asked questions

How many vulnerabilities does WordPress 7.1.5 fix?

Patchstack counts 20 fixes in the release: 18 vulnerabilities and two hardening changes. The issues include privilege escalation, SQL injection, cross-site scripting, denial of service and information disclosure.

Does the update include Gutenberg changes?

Yes. Patchstack says five fixes arrived through a Gutenberg package update and are in JavaScript packages. Its analysis advises reviewing those package changes as well as the documented core file list.

Which older WordPress versions have a patched release?

Patchstack says every branch still receiving security fixes has a patched release, going back to version 4.7. WordPress 4.6 and earlier no longer receive security updates.

Next step: check each site’s installed WordPress branch, apply its available security update, and review account access on sites with Contributor-level users or multisite administration.

Leave a Reply

Your email address will not be published. Required fields are marked *