WordPress 7.1.3 shipped on October 6, 2026 with seven security fixes and four bug fixes, including stored XSS on the Comments screen and a second-order SQL injection in the WXR export.
Table of Contents(6 sections)
Key Takeaways
- WordPress 7.1.3 was released on October 6, 2026 as a maintenance and security release, with 7 security fixes and 4 bug fixes, according to the official WordPress.org announcement.
- The fixes include a stored cross-site scripting (XSS) issue on the Comments admin screen, a second-order SQL injection in the WXR export, a denial-of-service issue and an information disclosure that let logged-out visitors see comments on private posts.
- WordPress.org recommends updating immediately. Sites with automatic background updates should receive it on their own, but it is worth confirming.
- Security fixes are being backported to older branches still eligible for security updates, currently back to 4.7.
What Happened
On October 6, 2026, WordPress.org published WordPress 7.1.3. It followed 7.1.1 and 7.1.2 in September. The release fixes seven security issues, each credited to the researcher who reported it:
| Issue | Area | Reported by |
|---|---|---|
| Stored XSS via pending comments | Comments admin screen | Trail of Bits with OpenAI |
| Denial of service | WP_Http::make_absolute_url() | Anthropic |
| Second-order SQL injection | WXR export | Anthropic |
| Authors could make posts sticky | Post permissions | Anthropic |
| Comments on private and unpublished posts visible to logged-out users | Comments | Ananda Dhakal, Patchstack |
| XSS in Imgur embeds | Embeds | Zhengyu Liu, Jingcheng Yang, Gavin Zhong |
Forgeable parameters passed to the {status}_{type} hook | Hooks | Alex Concha, WordPress security team |
Why it matters for SEO
A hacked site is an SEO problem as much as a security one. Injected spam links, cloaked pages and redirects can get pages flagged in Search Console's Security issues report and pulled from results. Keeping core, themes and plugins patched is the cheapest protection there is.
The comment-related fixes matter most for sites that accept comments, including WooCommerce stores with product reviews.
CUSTOM SEO DIAGNOSTIC · WORDPRESS
How Does "WordPress 7.1.3 Security Release: 7 Fixes, Update Now" Apply to Your Website?
Send me your URL and I'll check your site personally against what you just read — technical bottlenecks, competitor gaps, and whether Google's AI names you or them. Free reply within 24 hours.
What to do
- Check your version. In the WordPress dashboard, go to Dashboard › Updates. You want 7.1.3 or later.
- Update now if you are behind, after a backup. Most hosts let you take one from their control panel.
- Confirm automatic updates are on for minor and security releases.
- Check Search Console under Security & Manual Actions › Security issues if you suspect the site was compromised before you patched.
- Review user roles. Two of the fixes involve what lower-privileged accounts can do; remove accounts that no longer need access.
Quick Answers
When was WordPress 7.1.3 released?
October 6, 2026.
How many vulnerabilities does WordPress 7.1.3 fix?
Seven security issues, alongside four bug fixes.
Will my site update automatically?
Sites with automatic background updates enabled should update on their own. Check Dashboard › Updates to be sure.
Sources
- WordPress 7.1.3 Maintenance and Security Release — WordPress.org, October 6, 2026.
- Version 7.1.3 — WordPress.org documentation.
Last verified: 27 October 2026.

Mubashar leads SearchPrex’s founder-led SEO work for law firms, local businesses and ecommerce brands. He combines technical audits, Search Console data and local market research to build practical search strategies, with more than five years of hands-on experience across 20+ clients.
Join the Discussion or Request Our Next Topic
Share your perspective in the public thread below, or tell us what SEO teardown, case study, or update regarding WordPress 7.1.3 Security Release: 7 Fixes, Update Now you want us to cover next.
Community Perspectives (0)
Loading discussion...