The Code Behind About 70% of Websites Gets a Critical Security Fix Today. Will Your Site Be Updated?
If your website runs on WordPress, WooCommerce, Magento or Laravel, it runs on PHP. Today, 19 November 2026, between 14:00 and 14:30 UTC (16:00–16:30 in Israel), the PHP project releases security fixes for every supported version, and it rates the most serious flaws as critical. The practical step for a site owner is simple: ask your hosting company or developer today when the new PHP version will be installed on your site, and who will check that the site still works afterwards.
What happened
On 18 November 2026 the PHP security team posted an advance notice on the official PHP website. It said the regular four-week release would "address security vulnerabilities affecting all supported PHP versions" and that "the highest severity is CRITICAL."
The same notice adds an important limit: the critical issues "require either non-default configuration or uncommon setups." PHP said that the technical details and the fixed version numbers would be published together with the releases, not before. The notice was also shared on the oss-security mailing list.
The Register reports that PHP runs on about 70 percent of websites. That figure is The Register's, not a count we made ourselves.
The one flaw that is already known
The Hacker News and The Register both expect the release to include CVE-2026-115560, a remote code execution flaw in PHP's session upload progress feature. It only works when two things are true:
- the application's settings use the
php_binaryorphp_serializesession handler, and its code switches the handler tophpat runtime before starting the session; and - session upload progress is turned on.
The PHP Foundation told The Register in October that this combination is very unlikely in practice. Its interim advice was to set session.upload_progress.enabled=0 and restart PHP until the fix arrived. If your developer has not done that, today's update is the cleaner fix.
Why site owners should still pay attention
"Uncommon setup" is not the same as "no risk." Most small businesses never look at their PHP settings, so they cannot know whether their site is the uncommon one.
There is also recent history. In October, PHP fixed two other critical flaws known as PHP2Shell (CVE-2026-109618 and CVE-2026-109619). According to The Register, CISA added them to its Known Exploited Vulnerabilities catalog on 26 October, and The Hacker News reports limited active exploitation against exposed management interfaces. Hunt.io found hundreds of exploit-related files, and people on underground forums were asking for working exploits. That is how a fixed bug becomes a product: once a patch is public, attackers compare old and new code, build tools, and trade or sell access to the servers they get into.
None of the sources we read report attacks on the new flaws in today's release.
Who updates PHP on your site?
This is the question most owners cannot answer. On shared or managed hosting, the host usually installs PHP updates, but often only for the PHP versions it still supports. On a VPS or your own server, it is your developer or nobody. We explain this split in more detail in what your host handles and what you still need to check.
A shared server is also a shared risk. When one layer of the hosting stack has a flaw, every site on it can be affected, as we saw in the shared hosting vulnerability in LiteSpeed.
What to check today
1. Ask your host two questions
When will the new PHP release be installed on my server? And is my site on a PHP version that still gets security fixes at all?
2. Ask your developer one question
Does our code change session settings at runtime, and is session upload progress turned on? If they are not sure, ask them to apply PHP's interim setting until the update is in place.
3. Test after the update
PHP updates rarely break sites, but plugins and older themes sometimes misbehave. Follow a short routine like the one in our guide to safe WordPress security updates: take a backup, update, then check the home page, login, forms and checkout.
4. See what strangers see
An update fixes the server software. It does not tell you what else your site exposes. A free website security scanner can show what an outsider can see from the internet, without logging in.
FAQ
Is my WordPress site in danger today?
PHP says the critical issues need non-default settings or uncommon setups, and no attacks on the new flaws had been reported when we wrote this. The safe move is still to get the update installed soon, because details become public with the release.
Do I need to do anything if I am on managed hosting?
Ask. Many hosts update PHP quickly, but some only patch the versions they still support, and older sites are often left on old PHP versions. Get a date from your host.
What is CVE-2026-115560?
It is a remote code execution flaw in PHP's session upload progress feature that only works with a rare mix of session settings and application code. PHP's interim fix is to turn off session upload progress until the update is installed.
The original version of this article is on the HackerMe Security blog.