Site administrator checking a WordPress 7.1.3 security update on a desktop monitor Site administrator checking a WordPress 7.1.3 security update on a desktop monitor

WordPress 7.1.3 fixes seven security flaws in October release

WordPress 7.1.3 is a security and maintenance release with seven security fixes and four bug fixes. Here is what was reported, how to update, and what the backport notice means for older branches.

WordPress 7.1.3 arrived on October 6, 2026, with seven security fixes and four bug fixes. The WordPress project recommends updating sites immediately. If you manage a WordPress installation, this release note explains what the fixes address, how to install the update, and what to know about security backports.

In brief: Update to WordPress 7.1.3 from the Dashboard or WordPress.org. The release fixes issues involving cross-site scripting, denial of service, SQL injection, permissions, private-post comments, embeds, and hook parameters. Five fixes came from reports involving Anthropic or OpenAI, alongside reports from other security researchers.

What WordPress 7.1.3 fixes

The release includes seven security fixes, but the announcement does not assign severity ratings to the individual issues. It identifies the affected areas and credits the people or organizations that reported them. Three reports came from Anthropic, and one came from Trail of Bits in collaboration with OpenAI.

  • A stored cross-site scripting (XSS) issue on the Comments administration screen could be exploited through pending comments. Trail of Bits reported it in collaboration with OpenAI.
  • A denial-of-service issue affected the WP_Http::make_absolute_url() method. Anthropic reported it.
  • A second-order SQL injection issue affected WordPress eXtended RSS (WXR) export. Anthropic reported it.
  • A weakness could let users with the Author role make posts sticky. Anthropic reported it.
  • An unauthenticated user could access comments on private and unpublished posts. Ananda Dhakal of Patchstack reported it.
  • Imgur embeds were vulnerable to XSS. Zhengyu Liu, Jingcheng Yang, and Gavin Zhong reported the issue.
  • Forgeable parameters passed to the {status}_{type} hook could cause an action name collision. Alex Concha of the WordPress security team reported it.

The WordPress announcement also lists four bug fixes, but it does not detail them in the release post. The headline number for site owners is the seven security corrections, which the project says should be installed immediately.

How to install the security release

From the WordPress Dashboard, open Updates and select Update Now. You can also download the release from the WordPress 7.1.3 announcement. Sites that support automatic background updates will begin updating automatically, according to WordPress.org.

For teams managing several sites, check that each installation has reached the updated version rather than assuming every site completed an automatic update. That is a practical way to confirm the project’s immediate-update recommendation has been followed. If an update is managed by a host or agency, confirm the update status with whoever maintains the site.

Backports cover older branches, with a support limit

WordPress says it is backporting the security fixes, where necessary, to branches eligible for security fixes, currently through the 4.7 branch. The announcement says those backports are in progress and will ship as they become ready. It also states that only the most recent WordPress version is actively supported.

That distinction matters for sites running older branches. A backport is not the same as active support for every older version, and the announcement does not say that all backports were ready on October 6. Site owners should check the version they run and apply the relevant security update when it becomes available. WordPress’s stated support position favors keeping installations on the latest version.

A third security release in three weeks

WordPress 7.1.3 was the third security release in the 7.1 branch in three weeks. Version 7.1.1 was released on September 17, followed by 7.1.2 on September 22, before this October 6 release.

Jake Spurlock led the 7.1.3 release, with more than 40 contributors involved, according to the release details. The announcement credits contributors for coordinating maintenance and security changes into the stable release. For site owners, the short interval between releases is a reason to keep update checks part of routine site maintenance, especially when WordPress labels a release as security-related.

WordPress 7.1.3 FAQ

Should I install WordPress 7.1.3 now?

Yes. WordPress.org recommends updating sites immediately because this is a security release. Use the Dashboard’s Updates page or download the release from WordPress.org.

How many security fixes are in WordPress 7.1.3?

The release contains seven security fixes and four bug fixes. The announcement names all seven security issues but does not provide details about the four bug fixes.

Will WordPress backport the fixes to older versions?

WordPress says security fixes are being backported where necessary through the 4.7 branch, with updates to ship as they become ready. Only the most recent WordPress version is actively supported, so check your installation and move to the latest version when possible.

Check the Updates page on each site you manage and confirm that the security release has been installed.

Leave a Reply

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