Skip to content
Maintenance and security

WordPress 7.1.5: 20 Security Fixes and the CISA-Listed 7.1.4 Flaw

WordPress 7.1.5 brings 20 security fixes, three weeks after an actively exploited core flaw was fixed in 7.1.4. Check your version, update safely and look for signs of a break-in.

Harsh PrajapatiFull stack developer
Published
Updated
Reading time
11 min

WordPress 7.1.5: 20 Security Fixes and the CISA-Listed 7.1.4 Flaw

If your WordPress site is not on 7.1.5 (or 7.0.9 if you are still on the 7.0 branch), update it now. WordPress 7.1.5 came out on 18 November 2026 with 20 security fixes, including one that the release post says could let someone who is not logged in gain higher access and possibly run code on the server. It arrives three weeks after WordPress 7.1.4 fixed CVE-2026-119977, a core flaw the US Cybersecurity and Infrastructure Security Agency (CISA) lists as actively exploited.

This guide is for business owners: what changed, how to check your version, why automatic updates fail, and how to spot a site that was already hit.

What WordPress 7.1.5 fixes

The WordPress 7.1.5 release post (opens in a new tab) lists 20 security items. Two are hardening changes rather than known flaws: one deals with a malformed regular expression, and one removes the built-in Imgur embed. The rest fall into a few groups.

Type of issueExamples from the release postWho could use it
Gaining higher accessTemplate Part block attributes, which could lead to remote code execution; a multisite site admin taking over a Super Admin accountVisitors not logged in; site admins on multisite
Cross-site scripting (XSS)Shortcodes in comments, oEmbeds, media filenames, Customizer previewsFrom visitors not logged in to contributors and admins
SQL injectionWP_Meta_Query and the Customizer front page settingNot stated in the release post
Leaking informationPrivate taxonomy terms, user email addresses, author assignments, comments through the REST API and XML-RPCFrom visitors not logged in to editors
Denial of serviceBatched XML-RPC pingbacksVisitors not logged in

The release post does not give severity scores. The issues that need no login are the ones to worry about most, because anyone on the internet can try them. Others need a logged-in account, from subscriber up to administrator, which matters if your site lets people register, or has several staff logins, guest writers or old accounts nobody removed.

Security items fixed in 7.1.5
20
WordPress 7.1.5 and 7.0.9 released
18 Nov 2026
Planned date for WordPress 7.2
8 Dec 2026

WordPress also calls 7.1.5 a short-cycle release, with WordPress 7.2 planned for 8 December 2026. You do not need to wait for 7.2 to be safe. Update to 7.1.5 now and plan 7.2 separately.

The CISA-listed flaw from 7.1.4

On 3 November 2026, CISA added CVE-2026-119977 to its Known Exploited Vulnerabilities catalog (opens in a new tab), with a due date of 6 November for US federal agencies. CISA lists a flaw there only when there is reliable evidence of real attacks.

In plain words, the CVE text says WordPress briefly puts update files in predictable places reachable from the web during a full core upgrade, and an attacker who wins a race against the update can run their own code on the server. The WordPress 7.1.4 release post (opens in a new tab) describes it as a weakness in the upgrade process that "can lead to remote code execution during the upgrade window".

According to BleepingComputer's report (opens in a new tab), Wordfence said it blocked 13,095 attacks targeting this flaw in 24 hours. The attack depends on timing, so it is hard to pull off, but automated attacks only need to succeed once.

If your site is on 7.1.5, it has both the 7.1.4 fix and the new ones.

Which versions are affected

The WordPress releases page (opens in a new tab) lists 7.1.5 and 7.0.9 on 18 November 2026. The release post says the fixes are being backported to older branches, back to 4.7, and that some of those backports were not ready when it went out.

Your site runsStatusWhat to do
WordPress 7.1.5 or newerFixedCheck for signs of compromise if you updated late
WordPress 7.1.0 to 7.1.4Missing the November fixesUpdate to 7.1.5 now
WordPress 7.0.0 to 7.0.8Missing the November fixesUpdate to 7.0.9, then plan the move to 7.1
An older branch (4.7 to 6.x)Backport may still be on its wayUpdate to the latest release of your branch when it comes out, then plan a proper upgrade

Only the newest WordPress version is actively supported. Older branches get security backports, but a site on an old branch is still behind on everything else.

PHP security releases on 19 November

There is a second update this week, on the server rather than in WordPress. On 19 November 2026, PHP released security updates for every supported version: PHP 8.5.13 (opens in a new tab), 8.4.28, 8.3.37 and 8.2.36. PHP had warned the day before that the highest severity was critical, and that the critical issues need a non-default configuration or an uncommon setup.

Your server runsUpdate toNote
PHP 8.58.5.13Supported until 31 December 2029
PHP 8.48.4.28Supported until 31 December 2028
PHP 8.38.3.37Supported until 31 December 2027
PHP 8.28.2.36Security support ends 31 December 2026, so plan a move

The fixes cover parts of PHP common on WordPress hosting, such as PHP-FPM and sessions, plus others like SOAP and Phar. One critical flaw, CVE-2026-126714 (opens in a new tab), sits in the standard way PHP stores sessions and affects every supported version, though the advisory says an attacker would also need control over session data and a suitable weakness in the site's own code. PHP 8.6.0 came out the same day, but it is a new major version, not a security fix, so do not jump to it just for this.

Every WordPress site runs on PHP, so this one is for your host or developer. Ask them when they will apply it, and whether the host applies it for you on managed hosting. Some hosts and Linux vendors ship patched builds that keep an older version number, so if your number looks lower, ask whether the build includes the 19 November fixes. Last month's PHP2Shell vulnerability is a good reminder of why PHP updates matter as much as WordPress updates.

How to check your WordPress version

You can check your version in under a minute. Log in to WordPress and open Dashboard > Updates: it shows the version you are on and whether a newer one is available. The At a Glance box on the main Dashboard shows it too.

For more detail, open Tools > Site Health. The Info tab shows the exact version and the PHP version, and the Status tab runs a background updates test that warns you if something is stopping automatic updates.

If you run several sites, check each one. Include old landing pages and shops nobody logs in to.

Why your site may not have updated itself

Most sites should receive 7.1.5 automatically. The official guide to upgrading WordPress (opens in a new tab) says automatic updates are enabled on most sites by default, and the 7.1.5 release post says sites that support background updates update on their own. When a site is still behind, the usual reasons are:

  • Updates were switched off. A developer or plugin disabled automatic updates to "avoid surprises". The official guide strongly discourages this.
  • The host manages updates. Some hosts run core updates on their own schedule or need you to approve them in their control panel.
  • File permission problems. WordPress can only update itself if it may write to its own files. The official guide links failed updates to permission problems, and they can appear after a hosting move.
  • The site is deployed from code. Sites kept in version control often expect the developer to deploy updates.
  • Nobody is logging in. On a quiet site, a failed update warning can sit unread for months.

None of these show on the front of the site, which is why "it updates itself" is not a security plan.

The safe order to update

A security release such as 7.1.5 is lower risk than a major update, because it adds no new features. It does remove the built-in Imgur embed, so check any page that shows Imgur posts. A business site still deserves a short routine, because a failed update can take a site down.

  1. Full backup
  2. Update core
  3. Check key pages and forms
  4. Look for signs of a break-in
  5. Fix why auto-updates failed
  1. Take a full backup of the files and the database, stored away from the server, and make sure you know how to restore it. If you have no tested backup, website backup and disaster recovery sets one up.
  2. Update WordPress core from Dashboard > Updates, or through your host's panel if it manages updates.
  3. Check the pages that earn money: home page, contact and quote forms, checkout if you sell online, and logins.
  4. Look for signs of compromise, using the checklist in the next section, because the fix does not undo anything done before it.
  5. Fix the reason the update did not happen automatically, so the next security release reaches the site on its own.

If you are still behind on the 7.1 major update, our guide to WordPress 7.1 for business sites covers PHP requirements and staging tests.

Signs your site was already hit

Updating closes these doors, but it does not remove anything an attacker already planted. If your site sat on an old version through late October and November, spend ten minutes checking for these signs. CISA's required action for the 7.1.4 flaw mentions forensic triage as well as patching.

  • Unknown admin users. Open Users and filter by Administrator. Any account you do not recognise is a red flag.
  • New or changed files or plugins. Unfamiliar plugins, unfamiliar PHP files in the uploads folder or site root, or recently changed core files.
  • Redirects. Visitors, especially from Google or on phones, are sent to spam, betting or scam sites, while you see the normal site when logged in.
  • Fake pop-ups. A fake "verify you are human" or Cloudflare check that asks visitors to paste a command.
  • Warnings from outside. A Google "this site may be hacked" notice, a host suspension or emails you did not send.

If you find any of these, do not start deleting files. Take a copy of the site as it is, change passwords from a clean device, and follow the first steps in our hacked WordPress site cleanup guide.

When to get a professional cleanup

Get a professional when you find any sign of compromise, when the site takes payments or stores customer data, or when you cannot tell what changed. A cleanup that removes the visible symptom but misses the back door leaves the attacker a way back in.

Updating alone is a fair do-it-yourself job if you are on a supported version, have a working backup and the checks above show nothing unusual. Fixing why automatic updates stopped is a job for your developer or host.

SituationHandle it yourself?Better with help
On 7.0 or 7.1, backup works, no warning signsYes, update and checkOnly if updates keep failing
Very old WordPress or PHP versionNoUpgrade project with testing
Unknown admin user, redirects or pop-upsNoFull cleanup and hardening

If your site is down or shows signs of a hack, emergency WordPress fixes cover cleanup and recovery. If nobody is watching updates, website maintenance and support keeps core, plugins, PHP and backups current.

Where to start

Log in today and check three things: your version under Dashboard > Updates, the background updates result in Site Health, and your administrator accounts. If you are on 7.1.5 and all looks normal, confirm automatic updates are working for next time, and ask your host about this week's PHP update. If you are behind or something looks unfamiliar, back up first, then update or get help.

Frequently asked questions

Is WordPress 7.1.5 a security update?

Yes. WordPress.org released 7.1.5 on 18 November 2026 as a security release with fixes for 20 items, and recommends updating immediately. Sites with automatic background updates should update on their own.

I updated to 7.1.4 last month. Do I still need 7.1.5?

Yes. 7.1.4 fixed the flaw on CISA's list, but 7.1.5 fixes a new set of issues, several of which need no login. Update to 7.1.5, or 7.0.9 on the 7.0 branch.

Should I wait for WordPress 7.2 instead?

No. WordPress 7.2 is planned for 8 December 2026 and is a major update that deserves its own testing. Update to 7.1.5 now, then plan 7.2 when it is out.

Does the PHP security release affect my WordPress site?

Every WordPress site runs on PHP, so the PHP update matters too. PHP released 8.5.13, 8.4.28, 8.3.37 and 8.2.36 on 19 November 2026. PHP says the critical issues need a non-default or uncommon setup, but your host or developer should still apply the update soon.

Sources

The facts in this article were checked against these pages, last reviewed 20 November 2026.

  1. WordPress 7.1.5 Release, WordPress.org Newswordpress.org/news/2026/11/wordpress-7-1-5-release/
  2. WordPress 7.1.4, WordPress.org Newswordpress.org/news/2026/10/wordpress-7-1-4/
  3. Releases, WordPress.orgwordpress.org/download/releases/
  4. Upcoming Critical PHP Security Release, PHP.netphp.net/archive/2026.php#2026-11-18-1
  5. PHP 8.5.13 Released, PHP.netphp.net/archive/2026.php#2026-11-19-4
  6. PHP 8 ChangeLog, PHP.netphp.net/ChangeLog-8.php
  7. Supported Versions, PHP.netphp.net/supported-versions.php
  8. GHSA-fm2m-fjf5-v3cp, PHP security advisory on GitHubgithub.com/php/php-src/security/advisories/GHSA-fm2m-fjf5-v3cp
  9. Known Exploited Vulnerabilities Catalog, CISAcisa.gov/known-exploited-vulnerabilities-catalog
  10. Upgrading WordPress, WordPress Developer Resourcesdeveloper.wordpress.org/advanced-administration/upgrade/upgrading/
  11. CISA flags WordPress RCE flaw as actively exploited in attacks, BleepingComputerbleepingcomputer.com/news/security/cisa-flags-wordpress-rce-flaw-as-actively-exploited-in-attacks/
Harsh Prajapati, the author

Written by

Harsh Prajapati

Freelance full stack developer, founder of Worklancio

Web developer since 2018, freelancing since 2022. Builds WordPress sites and plugins, web apps and CRMs from Ahmedabad.

You may also like