Skip to content
← Blog
Search and websites ·

WordPress 7.1.3 fixes 7 security flaws. Keep your site current, calmly.

The October 2026 security release is a good moment to set a simple habit: update within days, check it applied, and review who can log in.

Laptop on an office desk showing a website admin screen, beside a checklist used to keep your WordPress site updated

To keep your WordPress site updated and secure, install each new release within days of it appearing, check that it has actually applied, and look at who has an account on your site. WordPress itself says "only the most recent version of WordPress is actively supported", so any older version you run is a risk you carry yourself.

This guide was prompted by WordPress 7.1.3, a maintenance and security release published on 6 October 2026 with 7 security fixes and 4 bug fixes. The WordPress News announcement says "it is recommended that you update your sites immediately". Patchstack's review of the release takes a calmer line: "Update as soon as you can, but this isn't a drop-everything emergency." We'd update within days, and use the release as a reason to check your user accounts.

Why the latest version is the only safe version

WordPress does send security fixes to older versions. They're backported, where necessary, to every branch still eligible for security fixes, which currently goes back as far as 4.7. That sounds generous, and it is a useful safety net. But the backports are still in progress and ship as they become ready. No dates are given.

The current release is different. It's the one WordPress actively supports, and it's the one that gets the fix first. If you're on 7.1.3, you have every fix in this release today; if you're on an older branch, you're waiting.

Releases can also arrive close together. WordPress 7.1.2 came out only two weeks before 7.1.3, and it fixed a single, serious vulnerability (CVE-2026-87902). That flaw let an unauthenticated visitor trigger a local file inclusion and, under the right PHP configuration, could lead to remote code execution. Two security releases in a fortnight is a good reason to make updating a habit. Waiting for a big one won't do.

What 7.1.3 fixes, in plain terms

WordPress lists seven security fixes and credits the people who reported them:

  • A stored cross-site scripting (XSS) flaw on the Comments administration page, exploitable through pending comments. Reported by Thomas Chauchefoin at Trail of Bits.
  • A denial-of-service issue in the WP_Http::make_absolute_url() method, which can tie up the server. Reported by Anthropic.
  • A second-order SQL injection in the WXR export, the tool that exports your content. Reported by Anthropic.
  • A weakness that let users with the Author role make posts sticky. Reported by Anthropic.
  • Comments on private and unpublished posts could be seen by anyone, without logging in. Reported by Ananda Dhakal from Patchstack.
  • Imgur embeds were open to XSS. Reported by Zhengyu Liu, Jingcheng Yang and Gavin Zhong.
  • Forgeable parameters passed to a WordPress hook could make one action look like another. Patchstack's example is a post given the status "delete" firing the same action as a real deletion. Reported by Alex Concha of the WordPress security team.

Some things aren't known. As Search Engine Journal points out, the official announcement gives no severity ratings or CVSS scores, doesn't describe the vulnerabilities, and says nothing about whether any are being exploited.

Patchstack's breakdown fills part of that gap. Two of the fixes start with an unauthenticated visitor: the leak of comments through the comment feed, and the comments XSS, which also needs a moderator to click. Three need a Contributor or Author account. One needs an administrator to run an export. One is plugin-dependent hardening.

Why your user accounts matter as much as the update

Most of these flaws need someone who can already log in. So the people holding Contributor, Author and higher roles on your site largely decide how exposed you were before the update. Patchstack's technical notes make this concrete.

Take the denial-of-service flaw. A loop that tidies up web addresses never finished on a relative path such as a//../b. A Contributor could trigger it through the block editor's link preview, simply by pointing the preview at a page they control. 7.1.3 stops the loop when a pass changes nothing.

The sticky-post flaw came down to one character. The REST API refused a request to make a post sticky only when the user lacked both of two permissions, edit_others_posts and publish_posts. Authors have publish_posts, so they passed. The fix changes "both" to "either".

The comments XSS is narrower than it first sounds. A link in a pending comment could carry code that ran when a moderator clicked it in the admin area. It relied on visitors being able to add a class to their comments, which only became possible in 7.1.0. Per Patchstack's review, the attack affects 7.1.0 to 7.1.2; the backports to older versions harden the same code.

The export SQL injection is narrower still. The vulnerable code has existed only since 6.5.0, and it's only reached when an administrator exports a single content type. The default "All content" export doesn't touch it. 7.1.3 makes sure featured-image IDs are treated as whole numbers at three points in the code.

Patchstack advises auditing who holds Contributor or higher roles. We agree, and it's the step that matters most for member organisations and agencies, where accounts build up over years: volunteers, past staff, freelancers, a client's former marketing manager. Open the Users screen, sort by role and ask of each account: does this person still need to log in, and do they need this level? Remove anyone who has left. Move people down a role where they only need to draft.

How to update, and how to check it worked

In your WordPress Dashboard, click Updates, then Update Now. You can also download 7.1.3 from WordPress.org and install it by hand, which some hosts and agencies prefer.

Sites that support automatic background updates will begin updating on their own. Neither WordPress nor Patchstack says when that will reach any particular site, so don't assume it has happened. Open the Updates screen and check the version number reads 7.1.3. If you manage several client sites, check each one.

If your site is on an older branch, the picture is less clear. WordPress says backports to every eligible branch back to 4.7 are in progress. Patchstack says the fixes have reached older branches through at least 6.6. Neither source gives a full list. Our advice is to plan the move to the current version now; waiting for backports to arrive isn't a plan. Test it on a staging copy first if your theme or plugins are old.

Two things to do after updating

First, clear your site's cache. The Imgur fix removes Imgur from WordPress's list of trusted embed providers. Trusted providers skipped the filter that reduces embedded content to a sandboxed frame, so text controlled by an Imgur uploader could appear on your page unfiltered. Patchstack notes that updating doesn't remove embed content WordPress has already stored, so an existing malicious embed keeps showing until the cache is cleared. If you use a caching plugin or your host caches pages, clear those too.

Second, upload a test image. One of the 4 bug fixes deals with image uploads failing with a fatal error on hosts that don't have PHP's DOM extension (ext-dom). WordPress strongly recommends that extension but doesn't require it, and WordPress 7.0 added code that used it without first checking it was there. The WordPress ticket says the upload process stopped completely. It was rated critical, though a core committer said it was probably rare: the code had been out for 134 days before anyone reported it. If your uploads have been failing since 7.0, this may be why, and a quick test confirms the fix.

Of the remaining bug fixes, two deal with embed endpoints that return a 404 message, and one stops the website icon in the admin toolbar growing to an enormous size.

Common mistakes with WordPress updates

One is assuming automatic updates have run. No one has said when they will reach a given site, and a site that missed one looks exactly like a site that didn't. Checking the version number takes a minute.

Another is treating a backport as the same as being current. A backport is a fallback that arrives when it's ready, on a version WordPress no longer actively supports. Being on the latest release is the only position where you know you have every fix.

The last is reading Patchstack's "not a drop-everything emergency" as permission to leave it for a few weeks. That phrase describes this release. The next one may be different, as 7.1.2 was.

None of this needs a developer for a typical site. The update is a button, the checks are a few minutes, and the account review is a cup of tea's worth of attention. Each decision stays with the person who runs the site.

Written with AI by Corantr Media Desk from its sources' facts, checked claim by claim, and approved by a person before it was published. How we write.

More from the blog