Skip to content
All posts
WordPress3 min read

WordPress 7.1.3 Released: 7 Security Fixes and 4 Bug Fixes

WordPress 7.1.3 landed on October 6, 2026 with seven security fixes and four bug fixes. Here is what was patched, who should update, and what plugin developers should check.

On this page
  1. What is in 7.1.3
  2. The seven security fixes
  3. How to update
  4. A checklist for plugin developers
  5. Recommended steps
  6. Source

WordPress 7.1.3 was released on October 6, 2026 as a maintenance and security release. It contains 7 security fixes and 4 bug fixes, and the WordPress team strongly recommends updating right away. This post summarizes what changed and what it means if you run sites or build plugins.

What is in 7.1.3

7.1.3 is a minor release on the 7.1 branch, following 7.1.1 (September 17) and the critical security release 7.1.2 (September 22). No new features are included. The focus is on closing security holes and fixing a handful of bugs.

The seven security fixes

The official announcement lists the following issues:

  1. Stored XSS on the Comments admin page, triggered through pending comments.
  2. Denial of service in the WP_Http::make_absolute_url() method.
  3. Second-order SQL injection in the WXR export feature.
  4. Privilege weakness that allowed users with the Author role to make posts sticky.
  5. Unauthenticated disclosure of comments on private and unpublished posts.
  6. XSS in Imgur embeds.
  7. Forgeable parameters in the {status}_{type} hook, which could cause action name collisions.

The announcement credits several outside researchers and security teams for reporting these issues, along with the WordPress security team.

How to update

Sites with automatic background updates enabled will update on their own. Everyone else can update manually in either of two ways:

  • Open Dashboard, then Updates and click Update Now.
  • Download the package from WordPress.org and deploy it as usual.

Security fixes are also being backported to older branches that still receive them, currently going back to 4.7, and those releases will ship as each backport is ready. Only the latest WordPress version is actively supported, though, so upgrading to 7.1.3 is the safest path.

A checklist for plugin developers

Several of these fixes touch areas that plugins commonly rely on, so it is worth a quick review after updating:

  • Comments and moderation: if your plugin renders or filters pending comments in the admin, make sure you escape output on your side as well.
  • Imports and exports: if you extend the WXR exporter or process exported data, treat stored values as untrusted when they are used in queries later.
  • Custom hooks: avoid building action names from user-controlled parts, and validate any dynamic hook name you construct.
  • Capabilities: double-check that features limited to editors and admins are protected by explicit capability checks rather than assumptions about roles.
  • Remote requests: if you resolve or follow URLs yourself, validate and limit them instead of trusting the input.
// Escape on output, even for data that came from WordPress itself.
echo esc_html( $comment_author );

// Always check capabilities before privileged actions.
if ( ! current_user_can( 'edit_others_posts' ) ) {
    wp_die( esc_html__( 'You do not have permission to do this.', 'your-textdomain' ) );
}
  1. Back up your site, or take a snapshot on your host.
  2. Update to 7.1.3 on a staging site first if you can, and test your key plugins.
  3. Update production and confirm that comments, exports and embeds work as expected.
  4. Review your own plugin code against the checklist above.

Source

For the full list and credits, see the official announcement: WordPress 7.1.3 Maintenance and Security Release.