
Your site runs on a WordPress version number you probably haven’t looked at since you installed it. You may not know that this number quietly decides which features work, how plugins behave, and which security holes remain open. It also decides whether your PHP and database are up to the job.
So what does it mean, which version should you run, and how do you check yours? Here’s the full picture.
As of November 3, 2026, the latest stable release is WordPress 7.1.4. WordPress released it on October 28, 2026, as a security update, so it’s worth installing soon.
TL;DR: WordPress 7.1.4 is the latest stable version, released October 28, 2026, and it’s a security update. Check your WordPress version under Dashboard > Updates, and check your PHP version under Tools > Site Health. WordPress 7.1 needs PHP 7.4 at minimum, and PHP 8.4 or 8.5 is recommended. Back up your entire site before you update, test risky sites on staging, and check your site afterward.
How to read a WordPress version number
Read 7.1.4 the way you’d read an address. The 7 is the major version. The .1 is the minor release within that major line. The .4 is the fourth maintenance update to 7.1.
Major releases bring new features and sometimes change behavior, so they deserve more testing. Minor and maintenance releases fix bugs and close security holes, and they usually leave your site’s behavior alone.

Pre-release builds also exist. Beta versions are early test builds, and release candidates are near-final builds. Both exist so developers can find problems early, and neither belongs on a live site.
What’s in 7.1.4
The official WordPress page lists 22 fixed vulnerabilities in this release. The most serious is a weakness in the update process itself that could lead to remote code execution. Most of the others are stored cross-site scripting bugs, which let attackers plant scripts that run in your visitors’ browsers.
Older branches received patches too. The official page lists fixed versions including 6.8.12, 6.7.11, 6.6.11, and 6.5.14. Versions 4.6 and earlier no longer receive security updates, and only the latest release gets full support.
📝 Note: Pantheon, a hosting platform, reported 13 security issues in its own summary of the release. We use WordPress’s official count of 22.
How to check your version
You have several options, so pick the one that fits your access.

- Dashboard > Updates is the fastest route. It shows your installed version and whether a newer one is available.
- The At a Glance widget on the main dashboard also displays the version.

- Tools > Site Health, then the Info tab, shows your WordPress version, your PHP version, and details about your server. It’s the best single screen for checking your environment.
- The BlogVault dashboard shows your WordPress and PHP versions on each site’s Site Details page, so you don’t need to log in to wp-admin. The same page includes an updates card for WordPress core, plugins, and themes, which is handy if you manage several sites.
- The page source can reveal the version too. Right-click a page, choose View Page Source, and search for
generator. You’ll find a line like this:
<meta name="generator" content="WordPress 6.5.3" />
Some themes remove this tag, and some owners hide it on purpose. If it’s missing, the version is hidden, and that tells you nothing about whether your site is current.
For server access, the version lives in wp-includes/version.php as a line like $wp_version = '6.9.5';. WP-CLI reports it directly with wp core version, and wp core check-update tells you whether a newer release exists.
PHP requirements: the part most people miss
WordPress runs on PHP, and your PHP version matters as much as your WordPress version. The official WordPress 7.1 server compatibility handbook sets the following.

- The absolute minimum for WordPress 7.1 is PHP 7.4. The minimums are MySQL 5.5.5 and MariaDB 5.5.5.
- The recommended versions for a new installation are PHP 8.4 or 8.5, with MySQL 8.4 or MariaDB 10.11, 11.4, or 11.8.
- WordPress 7.1 is compatible with PHP 7.4 through 8.5. Versions 7.4, 8.0, and 8.1 are end-of-life and kept only for backward compatibility.
That last point deserves attention. The handbook says a version that is end-of-life upstream is never recommended, even when WordPress still runs on it. If your Site Health screen shows an old PHP version, plan an upgrade with your host.

WordPress 7.0 raised the minimum from PHP 7.2.24 to 7.4 and dropped support for PHP 7.2 and 7.3, so older hosting setups are a common reason a site can’t update.
📝 Note: Check PHP before you update WordPress. A site on an unsupported PHP version can have trouble with the newest core release, and the fix is often a hosting setting rather than a WordPress change.
Multisite: one update, many sites
A WordPress multisite network has one shared core, so a core update affects every site in the network. The process has a few extra steps. Before updating, back up your entire multisite network, including shared files and every subsite’s database tables.
Network Admin > Updates is where core updates for the whole network live. The core code makes clear that you should only use the Upgrade Network screen after you’ve updated to a new WordPress version through the Updates screen. Clicking it before a core update doesn’t change anything.
Once the core update is in place, the Upgrade Network step applies the database updates to each site.. The code processes sites five at a time, so a large network takes longer. WordPress checks for core updates from the main site only, which avoids having every subsite nag you about the same update.

For a network, test on a staging copy of the whole network before you update, and check several subsites, not just the main one. A plugin that works on your main site can behave differently on a subsite with its own settings.
Beta versions and what’s next
WordPress 7.2 is the next major release. Its official schedule targets December 8, 2026, and the schedule page shows a window running to December 10. Beta builds and release candidates arrive before then.
Those builds are for testing on a separate copy. Pre-release code changes, and a live site is the wrong place to find out what changed.
How to update safely
Write down your starting point. Record your installed WordPress version, your PHP version, your active theme, and the plugins that handle payments, forms, or logins.
- Backup your site and test the restore. A backup you’ve never restored is a guess.
- Use a staging copy for risky sites. If your site runs a store, collects payments, depends on custom code, or is a multisite network, test on a copy first.
- Update from Dashboard > Updates. For a network, use Network Admin > Updates, then run the Upgrade Network step.
- Check what visitors actually do. Look at the front page, key posts, the login screen, forms, search, checkout, and any integration that matters to your business.
📝 Note: A successful core update proves that core finished installing. It doesn’t prove your plugins still work, so test the things visitors use.
Minor updates and major updates
A minor update is usually a quick job. A patch release like 7.1.4 mostly fixes bugs and security issues. For a simple site, a backup and a quick check may be enough. For a store, use staging.

A major update deserves more planning. Read the release notes, check that your plugins and theme support the new version, and test on staging. Don’t assume a plugin is fine just because it worked on the last major release.
What if the update breaks something?
Don’t run the same update again on a broken live site. Restore your tested backup, reproduce the problem on staging, and fix the cause there. The usual suspects are a plugin, a theme, custom code, or a PHP version that doesn’t match the new release.

If you can’t reach your dashboard, contact your host or developer before you move files around.
FAQs
What is the latest WordPress version?
WordPress 7.1.4, released October 28, 2026. It’s a security release, so install it once you’ve backed up and checked your site. Confirm the current number on the official WordPress version page, because releases change.
How do I check my WordPress version and PHP version?
Go to Dashboard > Updates for your WordPress version, and Tools > Site Health, then the Info tab, for both your WordPress and PHP versions. If you can’t log in, your host can confirm both numbers for you.
What PHP version does WordPress 7.1 need?
The minimum is PHP 7.4, but PHP 8.4 or 8.5 is recommended for new installations. Versions 7.4, 8.0, and 8.1 are end-of-life, so WordPress supports them only for backward compatibility. Ask your host to upgrade PHP before you update WordPress if your version is outdated.
How do I update WordPress on a multisite network?
Install the core update from Network Admin > Updates, then run the Upgrade Network step to apply database updates to each site. The Upgrade Network step only does its job after a core update, so don’t skip the first step. Test several subsites before you call the update finished.
Can I stay on an older WordPress version?
You can, but it leaves known security holes open. Older branches receive patches only for specific vulnerabilities, and WordPress no longer provides security updates for version 4.6 and earlier. Moving to 7.1.4 is the safest long-term choice.
The bottom line
Your WordPress version tells you how current your site is, how exposed it may be, and how much testing an update needs. Your PHP version decides whether the release can run at all. Right now, the target is WordPress 7.1.4 on a supported PHP version.
Check both under Dashboard > Updates and Tools > Site Health, back up before you change anything, update, and then check the things your visitors depend on.



