The WordPress latest version is 7.1.5, a security release published on 18 November 2026, and it sits on the 7.1 branch that launched on 19 August 2026. If your site runs anything older, the practical question is not only "what is new" but what keeping the site patched involves. Updates, testing and hosting that can run current software are recurring items in any realistic website cost.
This guide gives the latest WordPress version number, what changed across WordPress 7.0 and 7.1, and a lookup table that turns the version on your own Dashboard into an action. It reads the official release notes rather than blog summaries, and every version and date is as of 22 November 2026.
Quick Answer
The latest version of WordPress is 7.1.5 (18 November 2026). WordPress.org marks it a security release and says to update immediately; it fixes 20 vulnerabilities. Minor and security releases normally apply in the background within your own branch, unless updates are disabled or delayed, so open Dashboard > Updates to confirm what you are on. Move to a new major release such as 7.1 only after checking your plugins, theme and PHP version.
In This Post
Not sure which version your site is really on?
Send us your site address and what your Updates screen shows, and we will tell you whether the version is the problem or something else is.
Get a Site ReviewWordPress Latest Version: What Is Current Today
The current release is 7.1.5, and WordPress.org describes it as a security release. Its release notes state that "it is recommended that you update your sites immediately" and list 20 fixed vulnerabilities.
Those fixes are not all minor. The notes include an SQL injection in WP_Meta_Query, a multisite flaw that let a site Administrator take over a Super Admin account, and an unauthenticated privilege escalation through Template Part block attributes that could lead to remote code execution. WordPress.org does not publish a severity score in that notice, so treat the list as a reason to patch, not as a ranking.
The release archive shows how fast the 7.1 branch has moved. As the official releases page lists them, 7.1 arrived on 19 August 2026 and was followed by five point releases, 7.1.1 to 7.1.5, in three months. A site that was current in September is not current now.
| Release | Date | What it is |
|---|---|---|
| 7.1.5 | 18 Nov 2026 | Latest. Security release, 20 fixes |
| 7.1.4 | 28 Oct 2026 | Point release on the 7.1 branch |
| 7.1.3 | 6 Oct 2026 | Point release on the 7.1 branch |
| 7.1.2 | 22 Sep 2026 | Point release on the 7.1 branch |
| 7.1.1 | 17 Sep 2026 | Point release on the 7.1 branch |
| 7.1 | 19 Aug 2026 | Major release "Mary Lou" |
| 7.0.9 | 18 Nov 2026 | Courtesy backport of the same fixes to the 7.0 branch |
| 7.0 | 20 May 2026 | Major release "Armstrong" |
Takeaway
The WordPress latest version as of 22 November 2026 is 7.1.5, released 18 November 2026 with 20 security fixes. WordPress.org's notice says only the most recent version of WordPress is actively supported, so a site on an older release is relying on courtesy backports.
What Changed in WordPress 7.0 and 7.1?
WordPress 7.0 was the large editorial and platform release, and WordPress 7.1 refined the editing experience and moved image handling into the browser. Most of what the announcements list is editor, admin and developer tooling, so read them as changes to how you work in the dashboard.
The 7.0 announcement (20 May 2026) covers an AI Client in Core with an Abilities API, a refreshed dashboard, a Command Palette opened with Ctrl+K, a font management page, visual revision scrubbing, new Heading, Breadcrumbs and Icons blocks, and block-level custom CSS.
The WordPress 7.1 announcement (19 August 2026) adds the following:
- Responsive styling controls in the Site Editor, so layouts can be adjusted per screen size without custom CSS.
- A dedicated media editor for cropping, flipping, rotating and editing metadata.
- Notes with rich text and mentions for feedback inside the editor.
- New Playlist and Tabs blocks.
- Browser-based image processing: compression, resizing and thumbnail generation now happen in the browser, with support for formats including AVIF and HEIC.
The browser-side image change deserves a note for South African sites on shared hosting, because image processing moves from your server to the browser of whoever uploads the image.
The announcement says compression, resizing and thumbnail generation "now happen in the browser" and describes this as reducing server load; it does not publish a speed figure, so do not expect a number from it. If uploads fail afterwards, our guide to WordPress image upload errors covers the usual causes.
If you build pages with a visual builder, the block features above matter less than whether your builder is tested against 7.1. Our comparison of Elementor and Gutenberg covers that trade-off.
Should I Update WordPress? Match Your Version to an Action
Whether you should update WordPress depends on which kind of update is waiting: minor and security releases should go on promptly, while a major release deserves a short compatibility check first. The table below keys the decision to the version shown on your Dashboard, using only what WordPress.org's own notices state.
| Version you run | What the official notice says | What to do |
|---|---|---|
| 7.1.x below 7.1.5 | 7.1.5 carries 20 security fixes | Update now. This is a point release, so the risk of breakage is lowest. |
| 7.0.x | 7.0.9 contains fixes for all 20 vulnerabilities, but only the most recent version is actively supported | Take 7.0.9 today if you need time, then plan the move to 7.1.5 after a plugin check. |
| 6.0 to 6.9 | Backports exist, such as 6.9.12 and 6.8.13, as a courtesy. 6.5 to 6.9 are affected by all 20 issues; 6.0 by 18 of 20 | Treat the backport as a stopgap. The upgrade path to 7.x needs PHP 7.4 or newer. |
| 4.7 to 5.9 | Backports exist, such as 5.9.21 and 4.7.40. 5.9 is affected by 17 of the 20 issues; 4.7 by 11 of 20 | Fewer issues applying is not safety. A multi-version jump needs a full backup and a staged plan. |
| 4.6 or earlier | "No longer receive security updates" | No patch exists for these branches. Upgrade in stages or rebuild. |
The WordPress documentation itself says "You should always update WordPress to the latest version", and its updating guide adds the practical caveat: check that plugins and themes are compatible first, and note that "there isn't a single update order that works for every website."
Some sites will already be on 7.1.5. The same guide says most sites can apply minor and security updates in the background, and that you still have to click "Update Now" for major feature releases. That works within a branch, so a 7.0 site would be offered 7.0.9, not 7.1.5, and a site with updates disabled or delayed by the host stays behind. Open Dashboard > Updates and read the current WordPress version before assuming either way.
Takeaway
Should you update? For a point release inside your branch, yes, promptly. For a jump to a new major release, update after checking plugin and theme compatibility and your PHP version. Any site on 4.6 or earlier has no patch to apply, so it needs a staged upgrade or a rebuild.
Does an Out-of-Date Site Affect POPIA Compliance?
An unpatched site can make it harder to show reasonable security safeguards under POPIA, because section 19 requires safeguards to be kept current. This is a reading of the Act, not a legal opinion, and POPIA does not mention WordPress or any particular patching timeline.
Section 19(1) says a responsible party must secure personal information "by taking appropriate, reasonable technical and organisational measures" to prevent loss, damage and unlawful access. Section 19(2) adds that it must "ensure that the safeguards are continually updated in response to new risks or deficiencies in previously implemented safeguards", in the wording reproduced on popia.co.za, a secondary copy of the Act that you should check against the official text.
If your site stores contact-form enquiries, customer accounts or booking details, you hold personal information on it. The 7.1.5 notice names information disclosure bugs, including an "Author+ information disclosure exposing user email addresses via the REST API comments endpoint", which needs an Author-level login rather than being public, so the link to personal information is real but not unlimited.
A site with a documented update routine is simply easier to defend than one nobody has opened in a year. Adding two-factor authentication on WordPress logins is a sensible second safeguard.
How Do You Run a WordPress Update Without Breaking the Site?
A safe WordPress update is a backup, a compatibility check, the update itself and a visual check afterwards, in that order. The steps below follow the official updating guide, with a few practical notes of our own.
- Back up first. The guide says to back up so you can restore if something goes wrong. Confirm you can actually restore the backup, not only that one exists.
- Check plugins and themes. Open Dashboard > Updates and read the update notes for anything business-critical, such as booking, membership or payment plugins. Our guide to WordPress booking plugins is a good example of a plugin type where a failed update costs you appointments.
- Update during a quiet hour. WordPress puts the site into maintenance mode while it runs, which the guide says "usually lasts only a short time". Our maintenance mode explainer covers what visitors see.
- Click Update Now, then check the site. Visit the homepage, a form, a checkout or booking page, and the login screen. Then apply any remaining plugin and theme updates.
- Clear caching. After a manual update, the guide says to clear the cache so the new version shows immediately. If you use caching, clearing it after a one-click update is a sensible habit too.
If the site sticks on the maintenance message, WordPress.org's guide points to a leftover .maintenance file in the site root. It can be removed through FTP or your host's file manager once the update is no longer running.
If you see a fatal error instead, see WordPress critical error recovery mode. A monitor that alerts you when the site goes down, as set out in our website uptime monitoring guide, shortens the time you spend not knowing.
Worried an update will break a plugin you depend on?
List the plugins your site cannot live without and we will give you an honest view of which ones to test first.
Request a Plugin CheckWhat If My Host Will Not Offer the Update?
A WordPress version update may not appear because of an old PHP version, a host-managed update policy or disabled updates, and PHP is the first thing to check. WordPress 7.0 raised the minimum PHP version from 7.2.24 to 7.4, according to the WordPress hosting handbook, so sites on PHP 7.2 or 7.3 cannot take the 7.0 line or later without a PHP change first.
The minimum is not the target. WordPress.org's requirements page recommends PHP 8.3 or greater and MariaDB 10.11 or MySQL 8.4 or greater, and says PHP 7.4 and MySQL 5.5.5 still run WordPress but have reached end of life. The hosting handbook's 7.1 page recommends PHP 8.4 or 8.5 for new installs.
Changing PHP is usually a setting in your host's control panel, but it can break an old plugin, so take a backup first. Our guide to the WordPress PHP version update covers that process in full. If your host cannot offer a current PHP at all, that is a reason to review WordPress hosting options rather than keep patching around it.
Budget for this honestly. Ongoing maintenance, hosting and updates are recurring costs, and our breakdown of what a website costs to run per year shows where they sit.
Why South African Businesses Choose Growth Pulse Media
Growth Pulse Media is a Johannesburg agency led by Dirk van Greuning, who built and scaled a large South African ecommerce business before founding it. All work is executed in-house and the client load is kept limited so senior attention goes to each account. Our web design service page explains how we approach a site.
An honest read of your current site, including whether its age is the real problem, is a sensible first step.
Who This Is NOT For
This guide is for self-managed WordPress sites; it does not cover hosted builders, plugin vulnerabilities or promises about how an update will turn out.
You are on Wix, Squarespace or another hosted builder. The platform updates itself and none of these version numbers apply to you.
You want a guarantee that an update will cause no problems. No guide can promise that. WordPress.org's own advice is to back up and check compatibility, because the outcome depends on your plugins and host.
You need a plugin vulnerability report. The 7.1.5 notice covers WordPress core only. Plugins and themes have their own update notes.
Running an old site on cheap hosting?
Tell us what the site does for your business and where it is hosted, and we will audit it and tell you whether to patch, move or rebuild.
Request a Free AuditFrequently Asked Questions
What is the WordPress latest version?
The WordPress latest version is 7.1.5, released on 18 November 2026 as a security release. It belongs to the 7.1 branch, which launched on 19 August 2026. Check Dashboard > Updates to see what your own site is running.
Is WordPress 7.1 safe to update to?
WordPress 7.1 is the current major branch and receives point releases, with 7.1.5 the latest on 18 November 2026. Safe in practice means your plugins, theme and PHP version support it, so back up and check compatibility before the update. The official updating guide recommends both steps.
How often does WordPress release a new version?
The release archive shows WordPress 7.0 on 20 May 2026 and 7.1 on 19 August 2026, with point releases in between. The 7.1 branch alone had five point releases in three months, so expect frequent small updates between major versions.
Will WordPress update itself automatically?
Most sites can apply minor and security releases in the background, but only within their own branch, so a 7.0 site is offered 7.0.9 rather than 7.1.5. WordPress.org's guide says you still need to click Update Now for major feature releases. Disabled updates or a host's update policy can leave a site behind, so confirm in Dashboard > Updates.
What PHP version does the latest version of WordPress need?
The hosting handbook lists PHP 7.4 as the minimum for WordPress 7.1, and WordPress.org's requirements page recommends PHP 8.3 or greater. The handbook recommends PHP 8.4 or 8.5 for new installs.
What happens if I never update WordPress?
Your site keeps running, but known vulnerabilities stay open. WordPress.org says only the most recent version is actively supported, and versions 4.6 and earlier no longer receive security updates at all.
Get a straight answer on your site's update risk
Send us your site address and we will tell you what to prioritise, and whether your hosting or your site needs the attention. No obligation — we'll get back to you within 24 hours.
Talk to Growth Pulse Media

