Two security updates landed on WordPress sites this week, a day apart. WordPress 7.1.5 came out on 18 November 2026, and PHP, the language WordPress runs on, put out security releases on 19 November. They look like the same chore, but they belong to different people. On our own server, the WordPress fix installed itself 42 minutes after it was published. The PHP fix can’t do that, because it is part of the server, not the website. Here is what each update fixes, who has to act, and what we found when we checked.
What happened
WordPress 7.1.5 (18 November)
WordPress.org published 7.1.5 as a security release and wrote: “Because this is a security release, it is recommended that you update your sites immediately.”[1] The announcement lists 20 items. Patchstack counts eighteen of them as vulnerabilities and the other two as hardening changes.[2] Other security blogs count 18 or 19, depending on how they group them.
Most of the fixes need someone who can already log in, from a Contributor up to an Administrator. Two stand out because they don’t need a login to start:
- Comments. “Unauthenticated stored XSS via shortcode attributes in comments”.[1] Patchstack notes it also needs a page that shows a Latest Comments block.[2]
- Template parts. “Unauthenticated privilege escalation via Template Part block attributes that could lead to remote code execution”.[1] Patchstack explains that the attacker’s block has to be opened by a logged-in editor, so it can’t be triggered by a visitor alone.[2]
Patchstack also pointed out something that matters if you compare files by hand: “Five of the fixes come from a Gutenberg package bump rather than the core PHP backport”, so they are not in the official list of changed files.[2] When we checked on 19 and 20 November, none of the sources we read reported attacks using these flaws.
Older branches got fixes too. Patchstack writes: “Every branch back to 4.7 has a patched release”.[2] WordPress.org’s own version check, read on 20 November, lists 7.1.5 as the latest version. It treats 7.0.9 and 6.9.12 as patched and 7.1.4, 7.0.8 and 6.9.11 as insecure.[3]
PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36 (19 November)
A day later, PHP released security updates for every supported version. For 8.5, PHP.net says: “This is a security release. All PHP 8.5 users are encouraged to upgrade to this version.”[4] Patchstack counts 18 CVEs, seven of them rated Critical.[5] The day before, PHP had warned that “The issues rated CRITICAL require either non-default configuration or uncommon setups.”[4]
Patchstack’s summary for WordPress owners is the most useful line of the week: “None of these are WordPress bugs. They sit underneath it. This is a host-level update, and patching WordPress does nothing for any of it.”[5] It singles out two issues, a memory bug tied to how PHP writes its error log and a request-smuggling bug in PHP-FPM, and concludes that “two of them sit close enough to ordinary hosting that the PHP update should not wait for your next maintenance window.”[5]
Our view: one update is the site’s job, the other is the server’s
This section is our opinion. It is easy to treat “keep WordPress updated” as the whole of website security upkeep. This week shows why that isn’t enough.
- The WordPress fix is the website’s job, and WordPress does most of it for you. Its documentation says: “By default, automatic updates of WordPress are enabled on most sites.”[6] WordPress.org adds: “If you have sites that support automatic background updates, the update process will begin automatically.”[1] When a security release doesn’t arrive, it is usually because someone switched automatic updates off, or the site’s scheduled tasks stopped running. Nobody notices either until a week like this one.
- The PHP fix is the server’s job. No button in the WordPress dashboard installs it. On shared or managed hosting your host does it. On your own server or VPS, you or whoever runs it does. It also has to wait until the people who package PHP for your server publish the new version. That is why a PHP fix can lag days behind the announcement even on a well-run server.
The practical question for an owner isn’t “Did I update?” It is “Who updates which layer, and how would I know if they didn’t?” We covered the same split in October, with a server program that WordPress uses to preview PDFs.[7]
What we checked on our own server
We ran read-only checks on totalwebsolutions.co, which runs on our own hosting.
- WordPress: on 7.1.5. The update installed itself at 01:50 Malaysia time on 19 November (17:50 UTC on 18 November). The WordPress.org announcement went out at 17:08 UTC, so the update arrived 42 minutes later, with no one touching the site.
- PHP: on the morning of 20 November our server was still on PHP 8.5.12. The fixed 8.5.13 had been out for less than a day and had not yet reached our server. It goes on as soon as our server’s PHP packages include it.
- The request-smuggling bug: our server runs PHP through LiteSpeed’s own interface, not PHP-FPM. The PHP-FPM issue Patchstack describes needs FPM behind a front end that reuses FastCGI connections, so we read it as not applying to our setup. That is our reading of the advisory, not a test.
- The error-log bug: our server writes PHP errors to a file, which is one of the conditions Patchstack lists. So we are treating the PHP update as one that shouldn’t wait, in line with Patchstack’s advice.
Our own takeaway: the WordPress layer looked after itself within the hour. The server layer depends on people and on package timing, so it is the one worth following up.
Check it yourself
- Your WordPress version: go to Dashboard → Updates. You want 7.1.5. If your site is on an older branch, you want 7.0.9 or 6.9.12 at least.[3] If it still says an update is available a day after release, automatic updates are probably off or stalled on your site.
- Your automatic update setting: the same Updates screen shows whether automatic updates for WordPress itself are switched on. Security releases like this one are the reason to leave them on.
- Your PHP version: go to Tools → Site Health → Info and open Server. Compare the PHP version with the fixed versions: 8.5.13, 8.4.28, 8.3.37 or 8.2.36.[4] If yours is lower, ask your host when they will install it. If your PHP version no longer gets security fixes at all, ask them about moving up.
- Who can log in: Patchstack’s advice is to “audit who holds Contributor or higher on your sites. Six of these fixes are about what those roles can reach.”[2] Under Users, remove accounts for people who have left.
What not to do
- Don’t assume that updating WordPress also updated PHP. It didn’t. They are separate pieces of software.
- Don’t switch off automatic WordPress updates to “stay in control” unless someone is checking for security releases every week. This release shows how long a site can sit unpatched when nobody is.
- Don’t judge a release by its count. 18, 19 and 20 are all being quoted for the same release. What matters is whether your site is on a fixed version.
- Don’t install a PHP version yourself on hosting you don’t manage, and don’t jump to a brand-new major version (PHP 8.6.0 also came out on 19 November) just to get a security fix. The fix is in the newest release of the version you already run.[4]
Frequently asked questions
Does updating to WordPress 7.1.5 also fix the PHP security issues?
No. WordPress 7.1.5 fixes WordPress. The PHP issues are fixed by PHP 8.5.13, 8.4.28, 8.3.37 or 8.2.36, which your host or server administrator installs on the server.
My site is on an older WordPress branch. Do I have to move to 7.1?
Not for this fix. Patched releases came out for older branches too. WordPress.org’s version check lists 7.0.9 and 6.9.12 as patched, for example. Moving to the current version is still the better long-term choice.
Will WordPress 7.1.5 install itself?
On most sites, yes. Automatic updates for WordPress security releases are on by default. If your Updates screen still offers 7.1.5 a day after release, automatic updates are probably switched off or not running, and you should update by hand after taking a backup.
How do I find my site’s PHP version?
In WordPress, open Tools → Site Health → Info and expand the Server section. Your hosting control panel usually shows it too.
If you think your site is affected
We are a web design and SEO studio, not a cybersecurity firm, and we don’t offer security investigations or malware clean-up as a service. If you think your site is affected, contact your hosting provider and, for a plugin problem, the plugin’s maker first. If your site may have been hacked, use a specialist security service; the sources listed below explain what they will look for.
What we write here is what we check on the websites we build and host for our own clients. If you are planning a new website, or want a second opinion on your current site’s design and SEO, request a free written review.
References
- WordPress.org News, “WordPress 7.1.5 Release”, 18 November 2026. Accessed 19 November 2026.
- Patchstack, “WordPress 7.1.5 Security Release”, 18 November 2026. Accessed 19 November 2026.
- WordPress.org, core version check (stable-check). Accessed 20 November 2026.
- PHP.net, News archive 2026 (“PHP 8.5.13 Released!” and “Upcoming Critical PHP Security Release”), 18–19 November 2026. Accessed 20 November 2026.
- Patchstack, “PHP’s November 2026 Security Release: What Reaches WordPress”, 19 November 2026. Accessed 20 November 2026.
- WordPress Developer Resources, “Upgrading WordPress” (Configuring Automatic Background Updates). Accessed 20 November 2026.
- Total Web Solutions, “The WordPress Security Fix With No Plugin to Update”, 16 October 2026.
- Total Web Solutions records: read-only WordPress version, update time and PHP configuration check of totalwebsolutions.co, 19–20 November 2026.







