BLACK FRIDAY: 50% OFF all Pro plans Code: BLACKFRIDAY50
Pro from $10 a year or $30 lifetime, no code needed: Code: BLACKFRIDAY50
Ends Cyber Monday, 30 Nov. Lock in the price today. Code: BLACKFRIDAY50
Get 50% Off

WordPress 7.1.5 Security Update: What It Fixes and How to Check Your Elementor Site

WordPress 7.1.5 landed on 18 November 2026 with 18 security fixes and 2 hardening changes. Here is what it fixes, who should worry most, and a 15 minute plan to…
Red padlock on a black keyboard for the WordPress 7.1.5 security update

WordPress 7.1.5 came out on 18 November 2026, and it is a security release, not a feature update. The WordPress team says it is “recommended that you update your sites immediately.” If you run an Elementor site, a WooCommerce store or a handful of client sites, this is the update to install this week, not next month.

The good news: it is a small, safe update, and most sites will get it on their own. The less good news: a few of the fixed bugs can start with a visitor who is not logged in at all. In this guide we explain what WordPress 7.1.5 fixes in plain words, who should pay the most attention, and a 15 minute plan to update and check your Elementor site.

What WordPress 7.1.5 fixes

Laptop showing the WordPress logo on a blue surface

The official release post lists 20 items. Eighteen are security vulnerabilities and two are hardening changes, which is why you will see news sites say “18 fixes” while others say “20 issues”. Both are right. No CVE numbers had been assigned when the release went out, and none of the sources we checked reported attacks in the wild.

Here is the list grouped by who could trigger each problem:

Who can start it What was fixed
Anyone (no login) Privilege escalation through Template Part block attributes that “could lead to remote code execution”; stored XSS through shortcode attributes in comments (on pages with a Latest Comments block); denial of service through batched XML-RPC pingbacks; leak of private taxonomy terms through REST API search
Site Administrator on multisite Escalation from site Administrator to Super Admin through Customizer menu previews
Administrator SQL injection through the front page setting in Customizer previews; stored XSS through Customizer previews
Contributor and above Stored XSS through oEmbed provider responses, the Comment Date block date format and media filenames when a media block becomes a File block
Author, Editor or Subscriber accounts Leaks of user emails through the REST API comments endpoint, of commenter emails and IPs through XML-RPC wp.getComments, and an authorization bypass when editing comments
Other SQL injection in WP_Meta_Query through nested relation values; XSS through Openverse image metadata and in the Interactivity API context helper; reflected XSS in the legacy media popup

The two hardening changes fix a loose pattern that matched JSON media types too broadly and remove the Imgur embed variation from the block editor.

The most serious item is the Template Part bug. A visitor with no account can plant the attack, but it only fires when an editor or administrator opens the affected content. That is exactly the kind of bug that looks harmless until a busy site owner clicks the wrong thing.

Who should worry most

Code on a dark screen, the kind of core code patched in WordPress 7.1.5

Every WordPress site should update, but some setups carry more risk than others:

  • Sites with open comments. Two of the no-login bugs use comments and pingbacks. Blogs, news sites and stores with product reviews are the obvious targets.
  • Multisite networks. If you run a network for clients, a school or a team, the Administrator to Super Admin bug means one site owner could take over the whole network. Update these first.
  • Sites with many writers. Several fixes block stored XSS from Contributor and Author accounts. Agencies that give clients or freelance writers accounts should update quickly and review who has which role.
  • Sites that still use XML-RPC. Old mobile apps and some publishing tools still talk to WordPress through XML-RPC. Two of the fixes touch it.

If your site is a simple brochure site with comments turned off and one admin account, your risk is lower. You still need the update, because attackers scan for old versions in bulk and do not care how small your site is.

How WordPress 7.1.5 reaches your site

Security releases use WordPress automatic background updates. The release post says that on sites that support them, “the update process will begin automatically.” So many sites are already on 7.1.5.

Do not assume yours is one of them. Automatic updates can be switched off by your host, a security plugin, a line in wp-config.php or a management tool. Check the version yourself (the plan below shows how).

Two more details matter if you manage many sites:

  • Older branches. The fixes are being backported to every branch that still gets security fixes, back to 4.7. The release post says the backports “will ship as they become ready”, so a site on an older branch may get its patch a little later.
  • WordPress 7.2. WordPress 7.2 RC 2 ships with all the same fixes. The final 7.2 release is planned for 8 December 2026, so if you test 7.2 on a staging copy, refresh it to RC 2.

A 15 minute plan to update your Elementor site

Hand writing a checklist in a notebook before updating WordPress

A minor security release like WordPress 7.1.5 changes very little code, so it rarely breaks a site. Still, five minutes of care saves hours of panic. Here is the plan we use:

  1. Check your version. Go to Dashboard > Updates, or look at the “At a Glance” box on the dashboard. If it says 7.1.5, the update is done and you can skip to step 4.
  2. Make a backup. Use your host’s backup tool or your backup plugin. A backup from today is worth more than a perfect one from last month.
  3. Update WordPress. Click “Update to version 7.1.5” on the Updates screen. For several sites, use your host’s dashboard or your site management tool.
  4. Open the Elementor editor. Edit your home page and one other key page. Make sure the editor loads, the panel shows your widgets and the preview looks right. If styles look odd on the live site, clear your cache and use the Elementor Tools screen to clear or regenerate its CSS files.
  5. Test the money pages. Submit a form, add a product to the cart and reach the checkout if you run WooCommerce. Log out and view the site as a visitor.
  6. Update everything else. While you are there, update your theme and plugins. A patched core with an old plugin is still an open door.
  7. Tidy up user roles. Remove accounts nobody uses and lower roles that are higher than needed. On multisite, check the list of Super Admins and site Administrators.
  8. Turn off what you do not use. If no app or tool needs XML-RPC, ask your host or your security plugin to block it. If you use Imgur embeds, check that those pages still look right.

If the editor will not load after the update, the cause is almost always a plugin conflict or a stale cache, not WordPress 7.1.5 itself. Turn plugins off one by one on a staging copy until the editor works again.

Keep your site lean and up to date

Every plugin you add is more code to keep updated. That is one reason every Bright Addons block loads only where you use it, and why you can switch off the blocks you do not need.

If you are cleaning up your plugin list after this update, our three free plugins are all on WordPress.org: Bright Addons for Elementor (56 free widgets), Bright Addons Blocks Library (62 free blocks for the block editor) and Bright Addons for WooCommerce (28 free store modules). Browse the widgets and the blocks to see what each one does.

Need more? Bright Addons Pro for Elementor adds 98 Pro widgets (154 in total), and Bright Addons Blocks Pro gives you 161 blocks for Gutenberg. They are separate products with the same plans. During our Black Friday sale, plans start from $10 a year until 30 November 2026, with the discount already applied and no code needed. See every plan on the pricing page.

Conclusion

WordPress 7.1.5 is a quiet release with a serious job. It closes 18 security holes, including a few that start with a visitor who has no account, and it adds two hardening changes. Most sites will update on their own, but take five minutes to confirm your version, back up, update, and check that your Elementor editor, forms and checkout still work. Then update your plugins and tidy up user roles while you are there. Your site will be safer before the busy Black Friday weekend.

FAQ

Is WordPress 7.1.5 safe to install on an Elementor site?

Yes. It is a minor security release with targeted fixes, not new features. Back up first, update, then open the Elementor editor and test your forms and checkout to be sure.

Will WordPress 7.1.5 install automatically?

On most sites, yes. Security releases use automatic background updates. Some hosts, security plugins or wp-config.php settings turn these off, so check Dashboard > Updates to confirm your version.

Was any of these bugs used in real attacks?

The release post does not mention attacks, and the security sources we checked reported no active exploitation at release time. That can change once details are public, which is why updating quickly matters.

I am on an older WordPress version. Am I covered?

The fixes are being backported to every branch back to 4.7, and they ship as they become ready. The safest choice is still to move to the current 7.1 branch, after testing on a staging copy.

Share this post

Keep reading