WordPress 7.1.5 Fixes 18 Vulnerabilities, Including a Remote Code Execution Risk

WordPress 7.1.5 fixes 18 vulnerabilities, including one that could allow unauthenticated remote code execution. Site owners are urged to install the security update immediately.

· 4 min read · 4 comments

WordPress has released security update 7.1.5, fixing 18 vulnerabilities and adding two further security improvements. As Search Engine Journal reported on November 19, 2026, one of the flaws could have allowed unauthenticated remote code execution. WordPress is urging site owners to install the update immediately.

What’s been fixed

A vulnerability in Template Part block attributes could have allowed an attacker to gain elevated privileges without logging in and potentially execute code remotely. In that scenario, an attacker could run their own commands on someone else’s server. For a WordPress site, that could mean reading or changing files, accessing the database, creating administrator accounts, and planting malicious code. The source describes what the vulnerability could have led to but does not report any instances of exploitation.

Another issue was a stored XSS vulnerability in shortcode attributes within comments. XSS means malicious code could run in the browser of someone viewing an affected comment. Exploiting this flaw did not require a login. If an administrator viewed the comment, their account could be at risk.

The update also fixes two SQL injection vulnerabilities—flaws that allow an attacker to interfere with database queries. One affects nested relation values in WP_Meta_Query, which is used to build metadata queries. The other is tied to the homepage setting when previewing changes in the Customizer. The fixes span different parts of WordPress core: this release is not just about the vulnerability that could allow code execution.

Other risks and how to update

In Multisite, WordPress’s site network mode, a flaw in the Customizer’s menu preview could have given an administrator of an individual site super administrator privileges across the entire network. Unlike the two vulnerabilities described above, this scenario required an administrator account. If an attacker gained access to one on a single site, the consequences could extend across the network.

Other fixed issues include the possible exposure of users’ email addresses and private taxonomy terms. A separate flaw could have allowed users to edit comments beyond their permissions. A vulnerability in XML-RPC, which lets remote requests interact with a site, could have been exploited without authentication to disrupt the site’s availability.

Version 7.1.5 can be installed through the WordPress dashboard or downloaded; automatic updates are supported too. Security fixes are also available for affected earlier versions, but only the latest version is actively supported. WordPress recommends updating immediately. The article gives no installation deadlines for individual sites.

What this means for site owners

If your site handles menus, enquiries, or orders, this update is not just a developer concern: the flaws listed above affect administrative access, data security, and whether pages remain available. Some scenarios require no attacker account; for Multisite, the particular risk is that control of one site could become control of the entire network. Site owners should check which version is installed and ask whoever is responsible for the site to apply the available fix. Marketers do not need to understand how WP_Meta_Query works to see the implications: if access to the site is lost or the site goes down, published information and visitor enquiries are at risk. Developers, meanwhile, need to consider the full set of fixes, not just the vulnerability that could allow code execution. We previously covered the fixes in WordPress 7.1.4; this release needs attention in its own right.

My take

I would judge the urgency by which site operations could be put at risk, not by the number of fixes. The possibility of executing code without logging in, the risk to an administrator account, and disruption to site availability are reason enough to put version 7.1.5 ahead of the next copy edit. That is how I set priorities, not a claim that these flaws have already been used in attacks.

For my three bakeries in Tbilisi, what matters most is being able to update menus, cake-order information, and opening hours quickly. If the site is unavailable or control of it is at risk, the speed of those updates no longer matters. An off-the-shelf platform is good value as long as its standard features meet the business’s needs, but that value cannot be separated from installing security fixes promptly.

Sources

Where the news comes from. The text is a retelling in the author’s own words; the facts come from the source, the opinion is the author’s.

  1. WordPress 7.1.5 Security Release Fixes 18 Vulnerabilities via @sejournal, @martinibuster www.searchenginejournal.com

About the author

Elene Kiknadze

bakery chain owner

I have three bakeries in Tbilisi, and the website needs to handle menus, cake orders, and opening hours. I look at how quickly information can be updated first, and only then at the list of technologies.

All posts by the author

Leave a comment

Not published. We’ll send a link to confirm your comment.

No links or ads. Your first comment is published after review. By sending a comment you agree to the privacy notice.

  1. I manage a small ceramics studio site, and a security fix like this is a good reminder to keep maintenance time in the budget, even when the site is on a builder or WordPress. I’d ask whoever handles our updates to install 7.1.5 promptly and check that the booking and class schedule still work afterward—those are the parts customers rely on most. 🔒

    1. I’d push back on making this a maintenance-budget lesson for every builder site: the report flags a serious WordPress flaw, but doesn’t say it was exploited, and a separate API layer won’t make updates cheaper. Patch promptly, then smoke-test bookings and schedules—boring, effective ops.

      1. On a small practice project, I’ve learned to patch first and then quickly check the main user flow on mobile—so your booking-and-schedule smoke test feels like the right balance, even without assuming the flaw was exploited 🔒

      2. @ion.codes, in projects I’ve maintained, the useful budget wasn’t for a separate API layer but for someone to apply updates and verify the key flows; after a WordPress patch, a quick booking smoke test beats finding out from customers.