Skip to content

NVIDIA Member of the NVIDIA Inception program

Webfluence

All articlesWebsites

WordPress and PHP, the updates to do now

In one month, WordPress and PHP released critical security fixes. Here is what to check on your site, and in which order.

FrédéricNovember 21, 20265 min

The key points

  • WordPress 7.1.5, released on November 18, 2026, fixes serious flaws: install it without waiting.
  • PHP, the language WordPress runs on, fixed two critical flaws on October 21, then released new fixes on November 19.
  • PHP 8.2 gets no more security fixes after December 31, 2026: ask your host to move to a newer version.

Summarize withChatGPTClaudePerplexity

A small business site doesn't need to be famous to get attacked. Bots test every site, one by one, looking for an outdated version. November 2026 gave three good reasons to check.

What happened in one month

On October 21, the PHP team released versions 8.5.12, 8.4.27, 8.3.36 and 8.2.35 (php.net, October 21, 2026). They fix two flaws that let someone run code on a server without logging in. On November 19, a new round of security fixes followed.

On November 18, WordPress released version 7.1.5 (WordPress.org, November 18, 2026). It's a security release: it fixes several flaws, including one that lets a visitor who isn't logged in gain rights they shouldn't have.

On November 16, the FBI issued an alert about hacked WordPress sites used as bait, reported by Search Engine Roundtable (November 17, 2026). Attackers pick sites that rank well on Google, slip in trapped pages, and wait for an employee to find them while looking for a document template.

Over 1,000

hacked WordPress sites used as bait, according to the FBI alert of November 16, 2026

Why your site is concerned

A hacked site often keeps looking normal. The owner sees nothing. Meanwhile, Google may flag it as dangerous, and months of search rankings go with it.

The problem rarely comes from WordPress alone. It comes from the trio of WordPress, plugins and the PHP version at your host. Choosing the right tool matters, but follow-up after launch matters just as much.

A forgotten site doesn't stand still.It becomes an open door

The checks to do this week

In this order, in ten minutes

  1. A backup

    Before any update, check that a full backup exists and that it dates from today.

  2. WordPress

    In Dashboard, then Updates: the version shown should be 7.1.5 or newer.

  3. Plugins

    Update them, then delete the ones you no longer use. A deactivated plugin is still a risk.

  4. The PHP version

    In Tools, then Site Health, Info tab, Server section: look at the PHP version. At 8.2 or lower, write to your host.

  5. Google

    In Search Console, open Security and Manual Actions. A hacked site often shows up there before you notice it.

PHP 8.2: the date to remember

Every PHP version has an end date. For PHP 8.2, security fixes stop on December 31, 2026 (php.net, supported versions). After that date, a new flaw won't be fixed. Moving to PHP 8.3 or 8.4 is usually done in your host's client area, in a few clicks. Test the site right after: an old plugin may not keep up.

And WordPress 7.2

The next version is expected on December 8, 2026, according to the schedule published with its first release candidate (WordPress.org, November 17, 2026). That's no reason to wait: 7.1.5 fixes flaws right now.

What maintenance does

The sites we host are updated and monitored without you having to think about it. It's part of our website builds. If your site lives elsewhere, the free analysis tells you in a few minutes whether it is slow, outdated or poorly protected. And before a launch, keep our checklist at hand.

Backup, WordPress 7.1.5, plugins, PHP 8.3 or newer, Search Console: five steps, ten minutes.

Frédéric

Head of information systems

Frédéric runs hosting, maintenance and security for everything we put online. 30 years of software engineering.

Questions we get on this topic

  • They often cover WordPress, rarely every plugin, and never the PHP version. Check all three.

  • Yes, especially with an old plugin. That's why you back up first and test the site right after.

Read next to go further