Statistics · Info
What Changed in the Latest WordPress Release
Short answer
WordPress 7.1.5, released on November 18, 2026, is the latest WordPress release as of November 2026. It is a short-cycle security release that fixes 20 security items, including an unauthenticated privilege escalation that could lead to remote code execution, and it adds no new features. Update from Dashboard > Updates, or move to the patched version of your branch, such as 7.0.9 or 6.9.12.
Key takeaways
- WordPress 7.1.5, released November 18, 2026, is a security release with 20 fixes and no new features.
- The most serious fix closes an unauthenticated privilege escalation that could lead to remote code execution.
- The same fixes were backported to every supported branch, from 7.0.9 down to 4.7.40.
- Update from Dashboard > Updates, or download WordPress 7.1.5 from WordPress.org.
- WordPress 7.2 is next, with a final release scheduled for December 8, 2026.
What is the latest WordPress release?
WordPress 7.1.5 is the latest stable release, published on November 18, 2026.
It is a security release, not a feature release. WordPress.org's release post says the release features fixes for multiple issues and recommends that you update your sites right away.
The release before it, WordPress 7.1.4, shipped on October 28, 2026 with 13 security fixes, according to the WordPress Developer Blog. If you are still on 7.1.4, move to 7.1.5 now.
What did WordPress 7.1.5 change?
WordPress 7.1.5 fixed 20 security items and added no new features.
WordPress.org's version 7.1.5 documentation lists each item, with the person who reported it. The fixes cover the editor, the Customizer, the REST API, comments, XML-RPC, and multisite.
| Category | Items | Examples |
|---|---|---|
| Cross-site scripting (XSS) | 8 | Media library popup, Interactivity API, Comment Date block |
| Information disclosure | 4 | Private taxonomy terms, user email addresses |
| SQL injection | 2 | WP_Meta_Query, Customizer front page setting |
| Privilege escalation | 2 | Multisite Customizer, Template Part blocks |
| Hardening | 2 | JSON media type check, Imgur embed removal |
| Authorization bypass | 1 | Comment editing in the admin |
| Denial of service | 1 | Batched XML-RPC pingbacks |
Named fixes include a multisite privilege escalation that let a site Administrator take over a Super Admin account through Customizer menu previews. Another closes an SQL injection in WP_Meta_Query through nested relation values.
A third stops unauthenticated stored XSS through shortcode attributes in comments. The release was led by Jeremy Felt, Jerry Jones, and Jarda Snajdr.
Which fix matters most?
The most serious fix closes an unauthenticated privilege escalation that could lead to remote code execution.
The flaw sits in Template Part block attributes, and WordPress.org credits Logan Homolka with the report. “Unauthenticated” means an attacker needs no login, and remote code execution means code can run on the server.
The release post lists no CVE numbers or severity scores, so rank the fixes by the access they need. Items that need no login deserve attention first, and this one tops that list.
Did 7.1.5 add any new features?
No, WordPress 7.1.5 added no new features.
It is a short-cycle release, which means it exists only to ship security fixes fast. You will see no new blocks, settings, or screens after updating.
The one visible change is a hardening step: the block editor's Imgur embed variation was removed because its server-side provider is already gone, per the release post.
Which older WordPress versions got the same fixes?
The fixes were backported to every branch still eligible for security fixes, down to 4.7.
WordPress.org's documentation page lists a patched version for each branch, and only the most recent version of WordPress is actively supported. If your site runs an old branch, update to its patched version instead of staying on the old point release.
Our guide to how long a WordPress version is supported explains the support window in more detail.
| Branch | Patched version | Items fixed |
|---|---|---|
| 7.0 | 7.0.9 | 20 of 20 |
| 6.9 | 6.9.12 | 20 of 20 |
| 6.8 | 6.8.13 | 20 of 20 |
| 6.7 | 6.7.12 | 20 of 20 |
| 6.6 | 6.6.12 | 20 of 20 |
| 6.5 | 6.5.15 | 20 of 20 |
| 6.4 | 6.4.15 | 19 of 20 |
| 6.3 | 6.3.15 | 19 of 20 |
| 6.2 | 6.2.16 | 19 of 20 |
| 6.1 | 6.1.17 | 18 of 20 |
Branches older than 6.1 follow the same pattern, down to 4.7.40, which fixes 11 of the 20 items. WordPress 4.6 and earlier no longer receive security updates at all.
One extra change rode along: in WordPress 7.0, 1024-bit certificates were removed from bundled root certificates, and that change was applied to 6.9.12 and earlier as part of this release.
How do you update to WordPress 7.1.5?
Open Dashboard > Updates in your admin area and click “Update Now.”
That is the path WordPress.org gives in the release post. You can also download WordPress 7.1.5 from WordPress.org and install it by hand. Before you update, back up your site so you can restore it if anything goes wrong.
Sites that support automatic background updates start the update on their own. Check your site after the update and confirm the version shown is 7.1.5.
How do you check that the update worked?
After updating, open Dashboard > Updates again and confirm it shows WordPress 7.1.5 as the current version.
The documentation page lists 19 changed files and says no package was revised. You do not need to check those files yourself; the version number is the check that matters.
Developers can confirm the build another way: the release tag on GitHub is 7.1.5, commit 7be93a9, built from the 7.1.5 tag in the WordPress Subversion repository.
What comes after WordPress 7.1.5?
The next major release is WordPress 7.2, scheduled for December 8, 2026.
The first release candidate, RC1, arrived on November 17, 2026, and RC2 has also been released with all the 7.1.5 fixes included. WordPress.org's RC1 announcement confirms the final release date of December 8, 2026.
Planned highlights for 7.2 include a new default theme called Ipsum, a DataForm block settings inspector, faster media uploads, and modernized admin icons. PHP 8.6 compatibility improvements are planned too.
The Developer Blog's November 2026 roundup also notes a Secrets API, SVG admin icons, and a random-content URL in 7.2. Our guide to the WordPress release cycle explains how betas, release candidates, and final releases fit together.
Do not install a release candidate on a live site. Test it in WordPress Playground, which runs WordPress in your browser with no setup.
Did 7.1.5 change PHP requirements?
No, WordPress 7.1.5 changed no PHP requirements.
The release notes list no PHP change, and the fixes touch WordPress code only. The PHP change to watch is in 7.2, which adds PHP 8.6 compatibility improvements. If you are unsure about your PHP version, see whether WordPress supports PHP 8.4.
PHP.net's supported versions page shows PHP 8.2 security support ends December 31, 2026, while PHP 8.4 stays in active support until the same date. PHP 8.5 stays in active support until December 31, 2027.
Use the update as a prompt to check your PHP version. Our guide on which PHP version to use for WordPress walks through the choice.
What mistakes should you avoid?
Treat 7.1.4 as finished: update to 7.1.5 instead of stopping at the older release.
- Installing WordPress 7.2 RC1 or RC2 on a live site. Release candidates are for testing only, so use Playground or a test copy.
- Skipping the update because nothing looks different. Security releases change code under the surface, not screens you can see.
- Forgetting your plugins and theme. A patched core does not fix a weak plugin, so check each plugin for vulnerabilities after you update core.
- Waiting for a feature list. This release has none, and waiting for one leaves the 20 flaws open.
Frequently asked questions
Is WordPress 7.1.5 a major release?
No. WordPress 7.1.5 is a short-cycle security release that fixes 20 security items and adds no new features. The next major release is WordPress 7.2, with a final release scheduled for December 8, 2026.
Do I need to update if my site runs WordPress 6.9?
Yes. Update to WordPress 6.9.12, which carries all 20 of the 7.1.5 fixes. The fixes were backported to every branch still eligible for security fixes, down to 4.7, but only the most recent version is actively supported.
Will 7.1.5 change how my site looks?
No. You will see no new blocks, settings, or screens. The only visible change is the removal of the block editor's Imgur embed variation, which was a hardening step because its server-side provider is already gone.
What if my host has not applied the update yet?
Open Dashboard > Updates in your admin area and click Update Now. Sites that support automatic background updates start the update on their own, but a manual update works right away and takes only a few minutes.
Should I test WordPress 7.2 RC1?
Only on a test site or in WordPress Playground, never on a live or mission-critical site. Release candidates are still under development, and the final release of WordPress 7.2 is scheduled for December 8, 2026.
Where can I read the full list of fixes?
The WordPress.org documentation page for version 7.1.5 lists all 20 items, the people who reported them, the patched versions for older branches, and the 19 changed files.
Sources
- WordPress 7.1.5 Release WordPress News
- Version 7.1.5 WordPress.org Documentation
- WordPress 7.2 Release Candidate 1 WordPress News
- What's new for developers? (November 2026) WordPress Developer Blog
- Release Tag 7.1.5 GitHub (WordPress/WordPress)
- PHP: Supported Versions PHP.net
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
