WordPress 7.1.3 is a security release that patches seven vulnerabilities and four bugs. Here is a plain-English breakdown of the WordPress 7.1.3 security update — what each fix means for your site, plus a safe 15-minute update checklist so you can patch without breaking anything.
Table of Contents
What WordPress 7.1.3 actually fixed
WordPress’s official 7.1.3 release notes list seven security items and four bug fixes, and recommend updating immediately “because this is a security release.” WordPress publishes no CVSS scores with these fixes, so read the list below as seven doors that needed closing — ordered by how they reach your site, not by an invented severity rank.
| # | The flaw | What it means in plain English | Who is exposed |
|---|---|---|---|
| 1 | Stored XSS on the Comments admin page, via pending comments | A malicious link hidden in a pending comment could run scripts in your admin area — but only if a moderator clicks it | Sites with comments enabled and moderators reviewing a queue |
| 2 | Unauthenticated disclosure of comments on private and unpublished posts | Comments on drafts and private posts could be viewed without logging in | Any site with private or draft content that has comments |
| 3 | Second-order SQL injection in WXR export | A poisoned value sitting in the database could execute when an admin runs a site export | Admins who use Tools → Export |
| 4 | Imgur embeds vulnerable to XSS | Embedded Imgur content could bypass WordPress’s content filtering | Sites embedding Imgur media; needs a Contributor-level account plus someone viewing the embed |
| 5 | Author-role users could sticky posts | Author accounts could pin posts to the top of the blog — a privilege they should not have | Sites with multiple Author-level users |
| 6 | Denial of service in WP_Http::make_absolute_url() | A crafted request could tie up server resources | Needs a Contributor-level account |
| 7 | Forgeable {status}_{type} hook parameters | A plugin passing raw values into post creation could collide with other action names | Plugin-dependent hardening; affects specific plugin code patterns |
The release notes credit the reporters: Trail of Bits with OpenAI (item 1), Anthropic (items 3, 5, 6), Ananda Dhakal of Patchstack (item 2), Zhengyu Liu, Jingcheng Yang, and Gavin Zhong (item 4), and Alex Concha of the WordPress security team (item 7).

Worth a closer look: the comments XSS starts with an unauthenticated visitor — anyone can submit the malicious comment — but still needs a moderator to click a link inside it. Per Patchstack’s analysis, the root cause is jQuery’s $() processing link attributes from pending comments as HTML.
The Imgur flaw (item 4) has a cleanup step people miss: Imgur had been incorrectly whitelisted as a trusted oEmbed provider, letting its content skip sandbox filtering. Because oEmbed responses are cached, old embeds can persist after you update — if you have ever embedded Imgur media, clear your oEmbed caches afterward.
Also in this release: four maintenance fixes. One small sites will notice — if image uploads have been failing with a fatal error since WordPress 7.0, the culprit may be a missing PHP DOM extension, which 7.1.3 addresses. Test an upload after updating.
Should you panic? An honest risk read
No — but do not ignore it either. The evidence:
- No CVEs were assigned and no CVSS scores published — normal for WordPress minor security releases, and no reason for anyone to invent a severity label.
- No confirmed in-the-wild exploitation and no public proof-of-concept as of the week after release (SecurityOnline’s coverage).
- Patchstack’s verdict: “update as soon as you can, but this isn’t a drop-everything emergency” — only two of the seven flaws start with an unauthenticated visitor; the rest need Contributor- or Author-level accounts, an admin running an export, or specific plugin code.
That said, two facts argue against sitting on it. First, the pace: 7.1.1 shipped September 17 — closing WordPress 7.1.1’s Click2Shell attack chain — and 7.1.2 followed on September 22. When security releases come this fast, attackers know unpatched sites pile up quickly.
Second, the climate is unforgiving: on October 12, the UK’s AI minister called a breach of the country’s cyber defences “likely, if not inevitable,” noting two defensive AI pilots have already found and fixed 1,000+ vulnerabilities (BBC). You cannot control the threat landscape — but a patched site is one of the cheapest defenses you control. October’s plugin attacks show what happens without patching: the Ninja Forms hack planted hidden administrator accounts on unpatched WordPress sites.
Bottom line for small-business sites: update this week, verify it, and clean up accounts and caches while you are in there.
Before you click Update Now
Two minutes of preparation prevents most update disasters:
- Confirm you have a restorable backup of both files and the database — from your host’s snapshot tool, a backup plugin, or both. A backup only counts if the restore has been proven to work, so schedule a test restore this quarter if you never have.
- Note your current WordPress, PHP, theme, and plugin versions somewhere you can find if you need to roll back.
- Pick a low-traffic window. The update takes a minute or two and visitors see a brief maintenance message — just not during your busiest hour.
- If your site takes bookings, payments, or memberships, test on a staging copy first. For a simple brochure site with a contact form, a fresh backup plus a careful update is usually enough.
For stores, membership sites, or custom code, the professional workflow is staging-first: clone, update, test, then update production. This step-by-step update guide covers that sequence in detail.
The 15-minute safe update checklist
Step 1: Back up files and database

Back up now — not yesterday’s backup. Send it to offsite storage (Google Drive, Dropbox, S3) and wait for completion. Take a host snapshot too if available.
Step 2: Run the core update
In Dashboard → Updates, click Update Now under WordPress — core alone, not bulk-updated with plugins and themes, so you can isolate problems. Maintenance mode for a minute or two is normal. Run the “Database Update Required” prompt if it appears.
Step 3: Clear cached oEmbeds and purge your cache
Clear cached oEmbed data (your caching plugin or host panel has a purge option), then purge your full page cache so visitors get pages built by the new code, not stale copies of the old one.
Step 4: Verify the update worked
Confirm 7.1.3 in Dashboard → Updates; upload a test image (checks the PHP DOM-extension fix); open the Comments screen and confirm pending comments render; spot-check the homepage, contact page, and one form or checkout flow; view any pages with Imgur embeds.
Step 5: Tighten up while you are in there
Security releases are a good reminder to do the housekeeping you keep postponing:
- Review user accounts. The 7.1.3 sticky-post flaw involved Author-role users — remove or demote accounts nobody uses.
- Remove unused plugins and themes. Inactive plugins are code you are not patching.
- Update everything else a few items at a time, testing as you go (plugin update guide).
Step 6: Switch on automatic background updates
WordPress can install minor releases like 7.1.3 by itself, usually within a day — check Dashboard → Updates for the “automatically kept up to date” line. This site is on 7.1.3 because its background update installed it. If yours lacks that line, ask your host to re-enable it. Auto-updates do not replace backups, but they close the gap between release day and your next check.
Common mistakes to avoid
- Skipping the backup because “it is just a minor release.” Minor releases are exactly the ones that go wrong in boring, hard-to-diagnose ways.
- Bulk-updating core, plugins, and themes in one click. If something breaks, you will not know which update caused it. Core first, then the rest in small groups.
- Treating “no confirmed exploitation” as “safe forever.” It means no one has published an attack yet. The details are public in the release notes, and exploit authors read release notes too.
- Forgetting the database update prompt. If WordPress asks to update the database after the core files, do it immediately.
- Assuming an old branch is fine. Security backports reach as far back as 4.7, but they roll out after the main release — and only the latest version is actively supported. On 6.x or 7.0, plan the upgrade instead of waiting.
Frequently Asked Questions
Is the WordPress 7.1.3 security update critical?
WordPress calls it a security release and recommends updating immediately. In practical terms it is important, not an emergency: no in-the-wild exploitation is confirmed, and most flaws need an authenticated account or a specific user action. Update this week — but do update.
Are the WordPress 7.1.3 vulnerabilities being exploited in the wild?
As of the week after release, no. Security press covering the release confirmed there were no reports of active exploitation and no public proof-of-concept code. That can change, which is why the standard advice is to patch before exploit code appears, not after.
Will updating to WordPress 7.1.3 break my plugins or theme?
Minor security releases rarely break things — they patch specific flaws rather than changing features. That said, conflicts are always possible with complex setups, which is why the checklist above has you back up first and test on staging if your site takes payments or bookings. Update plugins and themes separately from core so you can isolate any issue.
My site is still on WordPress 6.x or 7.0. What should I do?
Plan an upgrade to the current version. WordPress does backport security fixes to older branches (currently as far back as 4.7), but those backports roll out after the main release, and only the latest version is actively supported. Staying on an old branch means waiting longer for every future fix. Back up, test on staging, and upgrade.
The bottom line
WordPress 7.1.3 closes seven real holes — two of them reachable by unauthenticated visitors — with no drama and no confirmed attacks in the wild. The correct response is equally undramatic: back up, update this week, clear your caches, and switch on automatic background updates so the next one installs itself. Fifteen minutes now beats an incident-response weekend later.
Sources: WordPress.org 7.1.3 release notes; Patchstack’s 7.1.3 technical analysis; SecurityOnline release coverage; BBC, October 12, 2026. All facts last checked October 13, 2026.
Was this article helpful?