Two security updates reached WordPress sites within a day of each other, and only one of them arrives through the WordPress dashboard. WordPress 7.1.5, released on 18 November 2026, fixes 18 vulnerabilities in core. A day later, PHP published security releases for branches 8.2 to 8.5, and PHP 8.6.0, out the same day, carries the same fixes.
The WordPress update is yours to apply. The PHP update usually belongs to your hosting provider, and it is worth asking them when it will happen.
The answer in brief
- WordPress 7.1.5 fixes 18 vulnerabilities and adds two hardening changes.
- The most serious is a privilege escalation through Template Part block attributes, which WordPress says could lead to remote code execution. An attacker needs no account, but an editor has to open the affected content, according to Patchstack.
- Every WordPress branch back to 4.7 has its own fixed release. Automatic updates start on their own, but check that yours ran.
- PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36 came out on 19 November 2026. PHP says its critical issues need non-default or uncommon configurations.
- Updating WordPress does not update PHP. Your host, your server packages or your container image does that.
- A site patched for PHP2Shell in October needs patching again.
- No attacks using either set of flaws have been reported.
What does WordPress 7.1.5 fix?
WordPress 7.1.5 fixes 18 vulnerabilities in core and makes two hardening changes, and WordPress recommends updating immediately. The release post gives no severity scores and mentions no attacks.
One issue sets the priority. A privilege escalation through Template Part block attributes can be started by someone with no account, and WordPress says it could lead to remote code execution. Patchstack’s analysis adds the condition that an editor then opens the affected content. Four more in the table can be started by a visitor who is not logged in, two of them only where a site uses a particular block or passes visitor input into a query.
If the table extends beyond the screen, scroll sideways to view all columns.
| Fix | Who can trigger it | Reported by |
|---|---|---|
| Privilege escalation via Template Part block attributes, possible code execution | Who can trigger itAnyone, no account, once an editor opens the affected content | Reported byLogan Homolka |
| Stored XSS via shortcode attributes in comments | Who can trigger itAnyone, no account, on a site with a Latest Comments block | Reported byRafie Muhammad |
| Denial of service via batched XML-RPC pingbacks | Who can trigger itAnyone, no account | Reported byGiovanni Cintolo |
| Private taxonomy terms exposed through REST API search | Who can trigger itAnyone, no account | Reported byAnthropic |
Information disclosure via XML-RPC wp.getComments |
Who can trigger itSubscriber and above | Reported byJaewook Lee |
| User email addresses exposed via the REST API comments endpoint | Who can trigger itAuthor and above | Reported byBen Bidner |
| Authorisation bypass in admin comment editing | Who can trigger itAuthor and above | Reported byJesse McNeil |
| Multisite escalation to Super Admin via Customizer menu previews | Who can trigger itAdministrator of one site | Reported byYuval Miller |
SQL injection in WP_Meta_Query via nested relation values |
Who can trigger itAnyone, no account, where a plugin or theme passes visitor input into the query | Reported byChristiaan Swiers |
| SQL injection via the front page setting in Customizer changeset previews | Who can trigger itAdministrator | Reported byRudy Faile |
The other eight vulnerabilities are seven cross-site scripting issues, four of which need a Contributor account or higher, and one that shows post and template author assignments to users with the Editor role or above. The two hardening changes tighten JSON media type matching and remove the block editor’s Imgur embed, whose server-side provider was already gone.
Which WordPress version do you need?
You need 7.1.5 on the current branch, or the fixed release for whichever older branch your site runs. WordPress backported the fixes to every branch that still gets security updates, which goes back to 4.7. All 20 changes apply to branches 6.5 and newer, and older branches are affected by fewer, according to Brandefense’s branch list.
If the table extends beyond the screen, scroll sideways to view all columns.
| Branch | Fixed release |
|---|---|
| 7.1 | Fixed release7.1.5 |
| 7.0 | Fixed release7.0.9 |
| 6.9 | Fixed release6.9.12 |
| 6.8 | Fixed release6.8.13 |
| 6.7 | Fixed release6.7.12 |
| 6.6 | Fixed release6.6.12 |
| 6.5 | Fixed release6.5.15 |
| 4.7, the oldest branch with a fix | Fixed release4.7.40 |
Sites with automatic background updates start the update on their own. Check that it finished, and on Multisite check every site. WordPress supports only its most recent version actively, so an older branch receiving this fix is a courtesy and not a reason to stay on it.
A host’s firewall rule is not a substitute. Pantheon added rules ahead of the release and says in its release note that they do not replace the update.
Is the October upgrade flaw still a risk?
Yes, for any site still on a release from before 28 October 2026. CVE-2026-119977 is a weakness in the core upgrade process that WordPress fixed that day in 7.1.4 and in a release for each older branch back to 4.7. CISA added it to its Known Exploited Vulnerabilities catalogue on 3 November, and Wordfence had blocked more than 240,000 automated attempts by early November, as Threat Defence’s analysis sets out.
The attack only works in the short window while core itself is updating, and Patchstack does not call it practical to exploit. It matters now because the 7.1.5 release sends a great many sites through a core update at the same time.
A firewall plugin that loads inside WordPress may never see the request. Block web access to wp-content/upgrade/ at the web server instead, before the core update runs, and afterwards look for administrator accounts you do not recognise.
What did PHP fix on 19 November 2026?
PHP fixed 17 vulnerabilities of its own across four branches, seven of them rated critical. The security releases are PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36, and PHP’s announcements encourage all users of each branch to upgrade. PHP 8.6.0, released the same day, includes the same fixes. PHP’s advance notice said the critical issues need non-default or uncommon configurations.
The count differs by branch and by who is counting. PHP 8.5.13 fixes all 17, 8.4.28 fixes 14, 8.3.37 fixes 13 and 8.2.36 fixes 12, going by PHP’s changelog. Some reports say 18, because 8.5.13 also updates a bundled library with a CVE of its own.
These are flaws in PHP, not in WordPress. No WordPress update touches them.
The release also closes two items left open after October. Our PHP2Shell news post covers the original pair of flaws and names CVE-2026-115560 as a further route, handled at the time by switching off session upload progress. The code fix is in these releases. So is a fix for CVE-2026-126714, a separate session flaw that the researchers at depthfirst call phpAfterShell and that October’s releases did not fix. A server updated for PHP2Shell in October therefore needs updating again.
Which PHP flaws can reach a WordPress site?
Two are worth acting on quickly for a typical WordPress site, and both depend on how the server is set up. That is the assessment in Patchstack’s analysis of the release, which rates each flaw for WordPress specifically.
If the table extends beyond the screen, scroll sideways to view all columns.
| CVE | Flaw | Reach on a typical WordPress site |
|---|---|---|
| CVE-2026-129289 | FlawRequest smuggling in PHP-FPM | Reach on a typical WordPress siteUncommon. WordPress meets the application-side condition on every REST request, but the web server must also reuse FastCGI connections |
| CVE-2026-129496 | FlawUse-after-free in the timezone cache | Reach on a typical WordPress siteUncommon. Needs a startup warning being written to a file-based error log. No login required |
| CVE-2026-126714 | FlawphpAfterShell: corrupted session files | Reach on a typical WordPress siteVery rare. WordPress core does not use PHP sessions, so the site would need a plugin that calls session_start() |
| CVE-2026-115560 | FlawSession serialiser mismatch | Reach on a typical WordPress siteVery rare, for the same reason |
| CVE-2026-129291 | FlawPrivilege escalation in PHP-FPM | Reach on a typical WordPress siteOnly after a site is already compromised, for example through a plugin flaw |
No attacks using these flaws have been reported. Italy’s CSIRT says proof-of-concept code for CVE-2026-115560 is available online, according to Precursor Security’s PHP tracker.
Who updates PHP, and what can you do until they have?
Whoever runs the server updates PHP: the hosting provider on shared or managed hosting, you or your developer on a cloud server or VPS. In WordPress, Tools, then Site Health, then Info, then Server shows which PHP version a site runs.
The fix is not everywhere yet. The official Docker php images carry the new versions, and Debian’s security tracker lists fixed packages for Debian 12 and 13. Ubuntu’s current releases, Red Hat, SUSE and Amazon Linux have not shipped fixed PHP packages, according to Precursor Security’s tracker. Distributions also backport fixes without changing the version number, so ask a host to confirm the fix by CVE and not by version alone.
Until the update is in place, three settings reduce the exposure:
- Session upload progress. Set
session.upload_progress.enabled=0in the server configuration, not in application code. The fixed releases turn it off by default, but an explicit setting in php.ini, an FPM pool or a hosting panel keeps it on. - FastCGI connection reuse. Turn it off with
fastcgi_keep_conn offin nginx, orenablereuse=offfor Apache’s mod_proxy_fcgi. - Startup warnings. Fix whatever makes PHP write warnings to its error log at startup, then restart PHP-FPM.
PHP 8.1 and earlier are end of life and get none of these fixes. PHP 8.2 is next: PHP’s supported versions page ends its security support on 31 December 2026. A site still on 8.2 should plan its move to 8.4 or 8.5 now.
Is there a plugin flaw to deal with too?
Yes, if the site uses WP STAGING or WP STAGING Pro. CVE-2026-109555, published on 19 November 2026 and rated 8.0 on CVSS, lets a logged-in user with only Subscriber access plant a malicious serialised object in their profile data. Nothing happens until an administrator runs a database restore or a staging reset, at which point the object can run code on the server, as OffSeq’s summary of the CVE record describes.
The CVE covers the free plugin up to version 4.17.0 and Pro up to 6.17.0. The WP STAGING page on WordPress.org lists 4.21.0 as the current version, with a changelog note that the release includes security hardening and that updating is strongly recommended.
The timing matters. Restoring a backup is what an administrator does when an update goes wrong, so update this plugin before the core update, not after.
Backup and staging plugins hold wide access to a site, which is why their flaws carry weight. Our UpdraftPlus incident guide covers what to check after attackers used stolen UpdraftCentral keys to install backdoor plugins.
What should UK website owners do now?
Update WordPress core now, then find out when your server’s PHP will be updated. In order:
- Update WP STAGING first, if you use it. Do this before any restore or staging reset.
- Block the upgrade directory. Deny web access to
wp-content/upgrade/at the web server, so the October upgrade flaw cannot be used during this or any later core update. - Update WordPress core. Go to Dashboard, then Updates, and confirm the site is on 7.1.5 or the fixed release for its branch. Do not assume the automatic update ran.
- Clear other pending plugin and theme updates. You are already logged in.
- Ask your host about PHP. Ask which PHP version the site runs, and when 8.5.13, 8.4.28, 8.3.37 or 8.2.36 will be in place. Ask them to confirm the fix by CVE.
- If you run the server yourself, update PHP. Restart PHP-FPM and rebuild any containers. Until then, apply the three settings above.
- Look for signs of compromise. Check for administrator accounts you do not recognise, and for plugins or files you did not install.
The core update is the priority because it closes flaws that an attacker with no account can start, on a server with no unusual configuration.
Web servers had their own urgent fixes in the same week. Our NGINX2Root guide covers the nginx and Apache HTTP/2 flaws and what to ask a host about them.
If you are not sure who updates your WordPress site or its PHP, talk to AIWIZ.