PHP Security Release November 19, 2026: What WordPress Agencies Should Do
PHP ships CRITICAL security fixes for 8.2 to 8.5 today. What we know, who patches PHP, and a readiness checklist for WordPress agencies.
On November 18, 2026, the PHP security team gave one day of notice: security releases for every supported PHP version ship on Thursday, November 19, between 14:00 and 14:30 UTC. The highest severity is CRITICAL.
Four weeks after PHP2Shell, the word “critical” is enough to make any agency nervous. This time, PHP adds that the critical issues “require either non-default configuration or uncommon setups.” This guide covers what you can do before the release, and what to check once it’s out.
Last updated: November 19, 2026, 12:30 UTC. PHP hasn’t published the fixed versions or CVE details yet. We’ll add the fixed version for each branch, the CVE IDs and the affected setups here as soon as it does.
TL;DR
- PHP releases security fixes for 8.2, 8.3, 8.4 and 8.5 today (Nov 19), between 14:00 and 14:30 UTC (15:00 to 15:30 CET).
- The critical issues need a non-default configuration or an uncommon setup. Fixed versions and CVE IDs come with the release, so any list you see before then is a guess.
- One step works today: for CVE-2026-115560, PHP advises setting session.upload_progress.enabled=0 until you’ve patched. If you set it during PHP2Shell, leave it on.
- Before the release, list each site’s PHP version and who patches it, check your backups and contact your hosts.
- PHP 8.1 and older get no fix from PHP. PHP 8.2 stops getting security fixes on December 31, 2026.
What PHP announced for November 19
PHP’s November 18 notice says the releases are part of its “regular four-week release cycle” and affect “all supported PHP versions”. On November 19, that means PHP 8.2, 8.3, 8.4 and 8.5, according to PHP’s supported versions page. “Technical details and fixed version numbers will be published alongside the releases.”
What we don’t know yet
PHP hasn’t said which version fixes each branch, how many issues there are or their CVE IDs, which part of PHP is affected, which setup the critical issues need, or whether the lower-rated ones affect default setups.
One loose end comes from October. When PHP published its informational advisory for CVE-2026-115560 on October 23, it promised the full advisory “with the next release”. No regular PHP release has shipped since, so today’s is the likely candidate. PHP hasn’t said whether that issue is rated CRITICAL.
What “CRITICAL” with “non-default configuration” means for a WordPress site
PHP’s written security policy rates issues High, Medium or Low. The “Critical” label in recent PHP advisories comes from CVSS, a standard score from 0 to 10: PHP2Shell’s two vulnerabilities scored 9.2, and CVSS calls anything from 9.0 up Critical.
That score measures how much damage a successful attack could do, not how many servers are exposed. So expect issues that are severe on the servers they affect, but that need a specific setup to work.
Why “uncommon setup” doesn’t mean “not my site”
An agency with 80 client sites rarely knows every server’s full configuration, and the WordPress dashboard won’t show you most of it:
- the php.ini values your host set on shared hosting,
- how PHP runs behind the web server (PHP-FPM, Apache mod_php, LiteSpeed),
- which PHP extensions are enabled,
- custom code a previous developer left behind, or a plugin that changes PHP settings while the site runs.
CVE-2026-115560 shows how this works. It needs a non-default session setting, plus code that switches it with ini_set() before the session starts. WordPress core doesn’t use PHP sessions, but a plugin or a custom theme can, and you can’t see either from wp-admin.
PHP2Shell hit default setups. This warning limits the critical issues to uncommon ones, so we’d treat this release as a scheduled patch: roll it out over the next few days and confirm it site by site. There’s no reason to take sites offline before PHP says what’s affected.
One setting you can change before the patch
For CVE-2026-115560, PHP recommends turning off a feature called session upload progress until the fix is installed: session.upload_progress.enabled=0. It’s the same setting PHP recommended on October 21 for PHP2Shell (CVE-2026-109619).
- If you or your host set it in October, leave it in place until every site is patched.
- If not, set it in php.ini, in the PHP-FPM pool or in the server configuration, then restart PHP. On Apache with mod_php, use php_admin_flag session.upload_progress.enabled off.
- On shared or managed hosting, you usually can’t change it yourself, so ask your host whether it’s already off.
Code can’t change this setting with ini_set(), so a plugin won’t do it for you. WordPress core doesn’t use PHP sessions, so turning it off doesn’t affect a standard WordPress site. If a site has custom upload features, test them afterwards.
Which PHP versions get the PHP security release
Only supported branches get PHP security updates. The table shows each branch’s status on November 19 and the share of WordPress sites running it.
| PHP branch | Status on Nov 19, 2026 | Security fixes until | Share of WordPress sites | Gets the Nov 19 fix from PHP? |
|---|---|---|---|---|
| 8.5 | Active support | Dec 31, 2029 | 6.8% | Yes |
| 8.4 | Active support | Dec 31, 2028 | 11.1% | Yes |
| 8.3 | Security fixes only | Dec 31, 2027 | 28.8% | Yes |
| 8.2 | Security fixes only | Dec 31, 2026 | 21.8% | Yes |
| 8.1 | End of life since Dec 31, 2025 | None | 8.9% | No |
| 8.0 and older | End of life | None | 22.6% | No |
Sources: php.net supported versions, php.net end of life branches, WordPress.org PHP version stats
According to WordPress.org’s statistics, 31.5% of WordPress sites report PHP 8.1 or older, which PHP no longer patches. Another 21.8% run PHP 8.2, which reaches end of life on December 31. If nothing moves, 53.3% of WordPress sites will run a PHP version without security support on January 1. WordPress itself recommends PHP 8.3 or greater.
Who updates PHP on a WordPress site
On October 21, PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35 fixed PHP2Shell, and the fix still had to reach each server before any site was safe. As WordPress.org puts it, “Your hosting company determines which versions of PHP are available for your site, and many hosters let you change this yourself.” In practice, someone patches the PHP build on the server, and someone else, often you, picks which branch each site uses.
Managed WordPress hosting
The host patches PHP across its platform. You follow its status page, confirm the rollout and choose each site’s branch.
Shared hosting
The host updates the PHP packages, and you can often switch the branch per site in the control panel. Ask when patched builds go live.
Your own VPS or cloud server
It’s you. Install the updated packages from your distribution or PHP repository, then restart PHP-FPM or the web server. On containers, rebuild on the updated base image.
Many portfolios mix all three. For every host you don’t control, send these questions today:
- When will the patched PHP builds be live on our servers?
- Where will you post the status: a status page, an email, a ticket?
- Will you restart PHP afterwards, so the new build is the one running?
- Is session.upload_progress.enabled already set to 0 on our servers?
- For any site still on PHP 8.1 or older, do you backport the fixes, or do we need to upgrade?
How to check a WordPress site’s real PHP version
- In WordPress: go to Tools > Site Health, open the Info tab, expand Server and read “PHP version”. The Status tab also flags an outdated PHP version as a critical issue.
- In the hosting panel: most panels show the PHP version per site, and that’s usually where you change it.
- Over SSH: php -v reports the command-line PHP, which isn’t always the build serving the site. Compare it with Site Health.
A version number can also hide a fix. Debian’s security FAQ explains that “instead of upgrading to a new release we backport security fixes to the version that was shipped in the stable release.” On those builds, check the package version against your distribution’s security notice.
A readiness checklist for agencies
Before 14:00 UTC
- Build the list. One row per site: PHP branch, host, hosting type and who patches PHP.
- Flag the outliers. Sites on PHP 8.1 or older get no fix today. Sites on 8.2 have six weeks of support left.
- Turn off session upload progress on the servers you manage, and ask your hosts about the rest (see above).
- Check your backups. Every site needs a recent, complete backup stored away from its server. On servers you patch yourself, take a manual backup right before the update.
- Contact your hosts. Send the questions above and bookmark their status pages. For servers you manage, book a maintenance slot after the release and check where your PHP packages come from (distribution or third-party repository).
When the release lands (14:00 to 14:30 UTC)
- Read PHP’s own pages first: the php.net news archive and the php-src security advisories. Note the fixed versions, the setup the critical issues need, and any mitigation.
- Match the conditions to your stack. If PHP names a setting, an extension or a server type, check which sites have it. Those go first.
- Patch the branch you already run. PHP 8.6.0 is due around the same time, and it’s a new branch, so leave it for later.
In the 24 hours after
- Confirm each site. Check the fixed version, or the patched package on distribution builds, or the host’s status page saying the rollout is done.
- Watch for side effects. After the PHP restart, check uptime and new PHP errors on every site you touched.
- Write it down. Note which site got which version on which date. It goes straight into your next client report as proof the work was done.
Before December 31: moving off PHP 8.2 without breaking client sites
Today’s release is a patch update. The PHP 8.2 end of life on December 31 is a branch upgrade, and the two carry very different risks.
| Patch update (for example 8.3.x to a newer 8.3.x) | Branch upgrade (for example 8.2 to 8.3 or 8.4) | |
|---|---|---|
| What changes | Bug and security fixes within the same branch | A new PHP version, with removed and deprecated features |
| Compatibility risk | Low | Real, especially for old plugins, themes and custom code |
| Who usually does it | The host or the server owner | Often you, from the hosting panel |
| Testing | Quick checks after the update: key pages, forms, checkout, PHP errors | Staging first, then production |
For branch upgrades, start from WordPress.org’s own process: back up the site, update WordPress, themes and plugins, check that your plugins are still maintained, and “if your hosting company offers a staging site, update PHP there first.”
Don’t stack two changes in the same window. Patch the branch each site runs today, then schedule the move to PHP 8.3 or later in batches, brochure sites first and WooCommerce stores last. Sites on 8.1 or older are already overdue, so put them at the top of that list.
Final thoughts
On paper, today’s PHP security release looks less dramatic than PHP2Shell. The bigger job is PHP 8.2, which more than one WordPress site in five (21.8%, per WordPress.org’s November 19 statistics) still runs. Agencies that use this release to map their portfolio can schedule those upgrades calmly before December 31.
Mapping dozens of client sites before the next PHP security release? WP Umbrella puts PHP version checks, backups, uptime and PHP errors for all of them in one dashboard.
Frequently asked questions about the PHP security release
PHP scheduled the security releases for Thursday, November 19, 2026, between 14:00 and 14:30 UTC, which is 15:00 to 15:30 in CET.
Yes. For CVE-2026-115560, PHP recommends setting session.upload_progress.enabled=0 until the fix is installed. On shared or managed hosting, ask your host to confirm it’s set.
No. The vulnerabilities are in PHP, the language WordPress runs on, so only a PHP update fixes them. Keeping WordPress, plugins and themes up to date still matters before you move a site to a newer PHP branch.
PHP says the CRITICAL issues need a non-default configuration or an uncommon setup, but hasn’t named them yet. Plan to install the update everywhere, and use the advisories to decide which sites go first.
Go to Tools > Site Health, open the Info tab and expand the Server section to see “PHP version”. If you want to check it for your full portfolio at once, you can do it with WP Umbrella. Find out more here: https://wp-umbrella.com/features/php-errors-monitoring/