This week's updates: WordPress 7.1.5 and a batch of nginx fixes

This week's updates: WordPress 7.1.5 and a batch of nginx fixes

November 19, 2026

Two of the most widely used pieces of web software, WordPress and the nginx web server, both shipped security releases this week. Here is what came out, what we did about it, and what it means if you run either one.

WordPress 7.1.5, applied within the hour

On November 18, WordPress released version 7.1.5 (and 6.9.12 for sites on the older 6.9 branch). It is a routine maintenance release, but it fixes 21 security issues, and the most serious ones could have let someone read or change a site's database content, or gain extra privileges, without logging in. None of them were reported as misused anywhere.

Within about half an hour of the release, we had gone through every WordPress site we maintain, eleven sites across four servers, and brought all of them to the fixed version: in each case we either confirmed WordPress's automatic background update had already run, or applied the update ourselves. That included one site where automatic core updates are deliberately switched off and which would otherwise have stayed behind indefinitely. Every manual update was preceded by a database and core-file backup, and followed by a file integrity check and a page-load check.

A batch of nginx fixes, with a short bridge to the real one

Also on November 18, the nginx project published fixes for a batch of ten security issues. The two most serious (CVE-2026-123007 and CVE-2026-123633) affected HTTP/2, a newer, faster way for browsers to talk to web servers, and in the worst case could have let someone run code on an affected server.

The same day, we upgraded the servers we maintain that run nginx from the project's own releases to the fixed 1.30.7 version, and verified their sites afterwards. For servers running Ubuntu's nginx packages, we checked which ones actually had HTTP/2 enabled: exactly one did. We turned HTTP/2 off on that server the same evening as an interim measure (it kept serving normally over HTTP/1.1, so visitors noticed nothing), and when Ubuntu shipped its fixed package the next morning (advisory USN-9159-1), we installed it and re-enabled HTTP/2 within two hours of the release. The remaining servers did not have the affected feature enabled, so they were not exposed to the serious issues, and they pick up the fixed package through routine automatic updates, which we verify rather than assume.

Separately, a security incident at a third-party web experimentation vendor made news this week. Some sites embed that vendor's scripts in their pages, so we checked every site we maintain: none of them loads those scripts, and there was nothing to do.

What this means for you

If you run WordPress, check that your dashboard shows 7.1.5 (or 6.9.12 if you are on the 6.9 branch), and confirm that automatic background updates are actually turned on. There can be good reasons to disable them, but then a person has to own the job of updating promptly.

If you run your own nginx, update to 1.30.7 or to your distribution's patched package. If you cannot update yet, disabling HTTP/2 removes the most serious risk in the meantime at a small cost in speed. And if someone else manages your hosting, it is fair to simply ask them what version you are on and when it was last updated.

Security releases like these are a normal part of running websites. What matters is keeping the gap between "fix released" and "fix installed" short, and that is exactly what this week looked like.

Need help with your website?

Our US-based dev team can fix issues fast — security updates, speed, bugs & more.

Request help now →