On this page (7 sections)

WordPress 7.1.5 was released on November 18, 2026 as a security release for WordPress Core. According to Wordfence, it fixes a broad group of security issues, and its headline puts the number at 19 vulnerabilities. Wordfence advises site owners to update immediately.

If you run a WordPress site, whether it is your own, a client's or a hosted fleet, this update belongs at the top of your list. Details are still limited, so this article separates what is confirmed from what is not, and focuses on how to check your version and update safely.

What is confirmed so far

The only source available at the time of writing is the Wordfence announcement. It confirms three things: WordPress 7.1.5 is a security release, it shipped on November 18, 2026, and it addresses a broad set of vulnerabilities in WordPress Core. Only one independent publisher covers the story so far, so treat the details as preliminary.

Just as important is what the research does not tell us. It gives no CVE identifiers, no CVSS scores, no breakdown of vulnerability types, no list of affected earlier versions, and no statement about active exploitation. We will not guess at any of these. Check the official WordPress release announcement and the changelog for the authoritative list as it becomes available.

Why a security release matters even without details

A Core security release usually bundles fixes for flaws that affect every site running that code, regardless of which themes or plugins are installed. When a release fixes this many issues at once, the safe assumption is that attackers and researchers will study the changes between versions. The window between a patch being public and someone building an attack on it tends to be short, so delaying the update has a real cost.

That said, a patch alone is not a sign that anything is being exploited. The source does not claim exploitation, so there is no need to panic. The sensible response is a prompt, tested update rather than an emergency rebuild.

Who is affected

The research does not list the affected version range. Until you confirm otherwise from the official release notes, assume any site running a WordPress Core version older than 7.1.5 should be updated. That includes:

  • Self-managed sites where you control updates and have automatic Core updates turned off
  • Agency and freelancer client sites that are pinned to a version or updated on a schedule
  • Hosting environments with staging copies and forgotten test installs, which are often missed
  • Multisite networks, where one outdated Core affects every site on the network

Sites on managed hosting may be updated for you, but do not assume it. Verify the version rather than trusting that it happened.

How to check your WordPress version

The quickest check is in the dashboard: the Updates screen shows your current version and whether a newer one is available. On the command line, WP-CLI can report it without changing anything.

Print the installed WordPress Core version (run from the site root, read-only)WP-CLI
wp core version

If the output is lower than 7.1.5, the site needs the update. To see whether WP-CLI also finds an available update, run the following read-only check. It lists available Core updates and changes nothing.

List available Core updates (run from the site root, read-only)WP-CLI
wp core check-update

What to do now

Plan the update like any Core change: back up, update, then verify. Do it first on sites that are public-facing or hold customer data.

  1. Make a full backup of files and the database, and confirm you can restore it
  2. Check your current version with the dashboard or wp core version
  3. Read the official WordPress 7.1.5 release notes for anything that affects your setup
  4. Update Core to 7.1.5 on a staging copy if you have one, and test login, forms, checkout and key pages
  5. Update production, then confirm the version again
  6. Update plugins and themes that have pending updates, since outdated components are a common way in
  7. Check that automatic background updates for Core are enabled, so future security releases arrive without delay
  8. Review administrator accounts and recent logins for anything you do not recognize

If you manage the site from the command line, the standard update command is below. Take a backup first.

Caution. A Core update briefly changes site files and may run database upgrades. Back up first, and avoid running it in the middle of a busy period such as a sale or checkout peak. Some plugins or themes can misbehave after a Core update, so test the key pages afterwards.
Update WordPress Core to the latest release (run from the site root after a backup)WP-CLI
wp core update
Confirm the version after updating; the output should show 7.1.5 or newerWP-CLI
wp core version

Detection and monitoring afterwards

Because the source does not say whether any of these issues were exploited, it is worth a short review after patching rather than assuming either way. Look for new or changed administrator users, unexpected files in the uploads folder, modified Core files, and unfamiliar scheduled tasks. The guide on how to check if a website is hacked walks through this, and what to do if your website is hacked covers the response.

For ongoing hygiene, the WordPress security checklist covers update habits, least-privilege accounts and backups. You can also run the free website malware scanner for an outside-in check, keeping in mind that outside-in detection has limits. A website firewall can add a layer of filtering while you roll out updates, but it is not a substitute for patching.

What we are still waiting on

As more coverage and the official changelog appear, look for the CVE identifiers, severity scores, the types of flaws fixed, and any word on exploitation. We will treat those as unknown until they are published by the WordPress project or a vendor. If your site runs plugins that matter to your business, the plugin vulnerability list is a useful companion for tracking issues outside Core.

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. WordPress 7.1.5 Security Release Fixes 19 Vulnerabilitieswordfence.com ·
  • WordPress
  • security release
  • WordPress core
  • patching
  • WP-CLI