Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared Managed Cloud India
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Best lists Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Setup & site building · Guide

How to Check Your WordPress Version

Short answer

The fastest way to check your WordPress version is to log in and open Dashboard > Updates, which shows the installed version and any available update. You can also read it in the At a Glance panel, under Tools > Site Health > Info, or by running wp core version over SSH. Compare the number with the latest release on WordPress.org, which is 7.1.5 as of November 2026.

Key takeaways

  • WordPress 7.1.5, released on 18 November 2026, is the latest stable release as of November 2026.
  • Dashboard > Updates shows your installed version and whether an update is ready.
  • Tools > Site Health > Info lists your WordPress version next to your PHP and database versions.
  • Running wp core version over SSH prints the installed version in one line.
  • Only the most recent WordPress version is actively supported.

Where is the fastest place to check your WordPress version?

Open Dashboard > Updates in wp-admin, where WordPress shows your installed version and any update that is ready.

Log in, then click Dashboard > Updates in the left menu. The page names the version you run and offers an Update Now button when a newer release is ready. The WordPress 7.1.5 release post describes the same path: visit the Dashboard, click Updates, then click Update Now.

If the page offers an update, read the release notes first. Version 7.1.5 was a security release, and WordPress advised site owners to update at once. Back up before you update, so you can restore the site if a plugin breaks.

Note the full number, including the third part. The difference between 7.1.4 and 7.1.5 is a set of security fixes, so quoting only 7.1 hides whether your site has them.

What does the At a Glance panel show?

The At a Glance panel on the main dashboard names your WordPress version and the active theme in one line.

Open the main Dashboard screen after logging in. The panel sits near the top and reads like WordPress 7.1.5 running Twenty Twenty-Five theme, with the numbers matching your install.

The Administration Screens guide from WordPress.org describes the dashboard as the place for recent activity and update information. If you do not see the panel, open Screen Options at the top of the screen and tick At a Glance.

How do you check the version in Site Health?

Open Tools > Site Health > Info, where the WordPress section lists your installed version.

Site Health has lived in WordPress since version 5.2, as the Make WordPress Core dev note on the feature records. The Site Health guide from WordPress.org places the screen under Tools > Site Health, with a Status tab that runs checks and an Info tab that lists facts about your setup.

Click the Info tab, then open the WordPress section. It lists the version, the site language, and the permalink structure, next to sections for the server, database, themes, and plugins.

This screen is useful when you ask a host or developer for help. It also shows your PHP version, and the WordPress requirements page recommends PHP 8.3 or newer as of November 2026. Our guide to checking your PHP version shows where to find that number on common hosts.

The Info tab has a copy button that puts the whole report on your clipboard. The Make WordPress Core dev note describes it as a way to share facts about your setup when you ask for support, without handing over passwords.

How do you check the version with WP-CLI?

Run wp core version over SSH in your WordPress folder, and it prints the installed version number.

Connect to the server, change into the WordPress root folder, and run the command. The wp core version reference shows that the command prints just the version number, such as 7.1.5.

Add --extra for more detail. The same reference shows that wp core version --extra also prints the database revision, the TinyMCE version, and the package language.

Pair it with wp core check-update to see if a newer release is ready. Jetpack's guide to checking your WordPress version lists wp core version as one of its methods for the same job.

How do you check the version in the site files?

Open wp-includes/version.php on the server and read the $wp_version line.

The file holds the version WordPress itself reads at run time. The wp core version reference notes that the expected database revision comes from wp-includes/version.php, which sits beside the version number.

Use this method when you have file access but cannot log in, for example when a bad plugin locks you out of wp-admin. Read the file, note the number, and compare it with the latest release on WordPress.org.

Do not edit version.php. Changing it will not update WordPress, and the next core update will overwrite it.

Why do plugin pages ask for your WordPress version?

Plugin pages list the WordPress version they were tested up to, so you can tell if a plugin fits your install.

Open any plugin page on WordPress.org and look for the tested-up-to line. Site Kit by Google version 1.192.0, updated on 16 November 2026, lists WordPress 7.1 as the version it was tested up to, according to its plugin page.

If a plugin was tested only up to an old version, it may still work, but the author has not confirmed it on your release. Check the plugin changelog and the WordPress version it needs before you install it.

WordPress itself warns you, too. Dashboard > Updates lists updates for core, themes, and plugins together, so one screen shows everything that is behind.

What does each part of the version number mean?

WordPress numbers releases as major, minor, and maintenance, so 7.1.5 is the fifth maintenance release of the 7.1 line.

Major releases add features and carry numbers like 7.0 and 7.1. Minor releases fix bugs and close security holes, and they add a third number, as in 7.1.5. The WordPress.org release archive groups releases by branch, with 7.1.5 listed under the 7.1 branch.

The WordPress 7.1.5 release post calls 7.1.5 a short-cycle release and names 7.2, planned for 8 December 2026, as the next major release.

Maintenance releases are safe to install quickly. Major releases deserve a backup and a check that themes and plugins still work, since they can change features.

Release dates help you judge the gap. If your site runs 7.1.0 from August and the latest is 7.1.5 from November, you missed three maintenance releases, and the newest one is a security release.

How do you know if your version is still supported?

Only the most recent WordPress version is actively supported, so compare your number with the latest release on WordPress.org.

WordPress states this plainly on the 7.1.5 release post: only the most recent version is actively supported. Security fixes for 7.1.5 were backported to branches back to 4.7, but those branches get no new features.

The release archive shows the pace. WordPress 7.1 arrived on 19 August 2026, 7.1.4 followed on 28 October 2026, and 7.1.5 on 18 November 2026. A version more than a few months behind the latest release is overdue for an update.

ReleaseDateType
7.119 August 2026Major
7.1.428 October 2026Maintenance
7.1.518 November 2026Security
7.28 December 2026 (planned)Major

Our guide on how long a WordPress version is supported explains the support window in more detail.

What should you do if your version is out of date?

Back up the site, update WordPress from Dashboard > Updates, then check the pages your visitors use most.

Take a full backup first. If an update breaks a plugin, the backup is your way back.

Click Update Now on Dashboard > Updates, or run wp core update over SSH. Automatic background updates handle minor releases on many sites, but check that they ran. The 7.1.5 release post notes that sites with automatic background updates start the update process on their own.

After the update, open the home page, a post, and any form or shop page. If something breaks, our guide to fixing a site broken after a WordPress update walks through the recovery steps.

Also check your PHP version. WordPress.org's requirements page recommends PHP 8.3 or greater, with MariaDB 10.11 or greater or MySQL 8.4 or greater. Older PHP 7.4 and MySQL 5.5.5 installs still run, but WordPress.org warns that those versions have reached end of life and may expose your site to security issues.

What mistakes should you avoid?

Do not trust a cached number, do not hide the version instead of updating, and do not update without a backup.

  • A stale dashboard page can show an old number. Reload Dashboard > Updates before you quote a version.
  • Hiding the version does not make a site safe. Our guide to hiding the WordPress version explains what it does and does not do, and updating is the real fix.
  • Do not judge a version by the theme or a plugin. A theme can claim support for a version your core does not run.
  • Do not update a live site late at night without a backup. If the update fails, you need time and a restore point.

Frequently asked questions

How often should I check my WordPress version?

Check it whenever you update, and glance at Dashboard > Updates at least once a month. WordPress ships maintenance releases often, and security releases like 7.1.5 deserve a same-day update. Enable automatic background updates for minor releases if you do not want to check by hand.

What is the difference between a major and a minor WordPress release?

A major release adds features and changes the second number, as in 7.0 to 7.1. A minor release fixes bugs and security issues and adds a third number, as in 7.1.4 to 7.1.5. Minor releases are safe to install quickly, while major releases deserve a backup and a plugin check first.

Why does my site show an old version after I updated?

The update may have failed, or a cached page may show the old number. Reload Dashboard > Updates and confirm the new number there. If it still shows the old version, check with your host whether automatic updates are blocked, then update by hand.

Is it safe to hide my WordPress version?

Hiding the version only removes a number from your page source, and it does not fix any security issue. Attackers can fingerprint a version in other ways. Keep WordPress updated instead, and treat version hiding as a small extra step, not a fix.

What PHP version should I run with WordPress 7.1?

WordPress.org recommends PHP 8.3 or greater, with MariaDB 10.11 or MySQL 8.4 or newer, as of November 2026. PHP 7.4 still runs WordPress, but it has reached end of life, so ask your host to move you to a supported PHP version.

Sources

  1. WordPress 7.1.5 Release WordPress News
  2. Release Archive WordPress.org
  3. Requirements WordPress.org
  4. Site Health WordPress.org Documentation
  5. wp core version WordPress Developer Resources
  6. Site Health Check in 5.2 Make WordPress Core
  7. How to Check Your WordPress Version Jetpack
  8. Site Kit by Google WordPress.org

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.

About the editors

WPLegible editors

Researched from the primary sources listed above and checked against our editorial rules. About the site · How we test