PHP Fixed 7 Critical Flaws: What to Ask Your Web Developer
On 19 November 2026 PHP fixed seven critical flaws, a month after PHP2Shell. What it means for a company website or online shop, and a ready message for your developer or host.
In 30 seconds
- What happens
- On 19 November 2026 PHP fixed a new batch of flaws. Seven are rated Critical; under some server settings they could let an outsider run code on a website's server.
- Who it affects
- Companies whose website, online shop or customer portal runs on PHP. That includes WordPress, WooCommerce, PrestaShop, Magento and Drupal sites.
- First step
- Ask your web developer or hosting company which PHP version each site runs, and get a written answer with the date of the update.
- Our view
- For a small company, this is not a technical project. It is one message to the person who runs your website, and a written answer back. The hard part is knowing who that person is for each site.
Facts checked on 22 November 2026.
PHP is the programming language behind a large share of websites and online shops. On 19 November 2026 the PHP project released versions 8.5.13, 8.4.28, 8.3.37 and 8.2.36 with security fixes, together with the new PHP 8.6.0. According to Wiz, a cloud security company, the release fixes 17 flaws, and seven of them are rated Critical: 9.2 out of 10 on the CVSS v4.0 severity scale.
This comes a month after PHP2Shell, two critical PHP flaws fixed on 21 October that attackers already try to use. If your site was not updated in October, it now misses two rounds of fixes.
Short answer
- Is my site affected? If it runs on PHP and has not been updated since 19 November, it runs a version with known critical flaws. Whether they can be used against your site depends on server settings that only your developer or host can check.
- How urgent is it? When Wiz published on 19 November, it had seen no attacks on the new flaws. The October flaws are already under attack. Update both in one go.
- What do I do today? Send the message below to whoever runs each site. Ask for the PHP version and the date of the update, in writing.
- What if we run PHP 8.1 or older? The PHP project no longer fixes these versions. Some hosting companies and Linux distributions backport fixes; ask yours, and plan a move to a supported version.
What could happen to a PHP website or shop
The worst case for a flaw like this is remote code execution: someone on the internet runs their own commands on your web server, without a password. On a shop or a portal, that server often holds customer details and orders, and it controls what your customers see.
Not every PHP site is exposed. PHP itself says the Critical flaws need a non-standard configuration or unusual settings. For example, one of them, CVE-2026-115560, needs three conditions at once: a session feature switched on, two parts of the site reading the same session data in different formats, and suitable code in the site that an attacker can misuse. Another, a flaw in PHP-FPM that can make the server read one request as two, needs both a web server that keeps its connections to PHP open, which is not the default, and a part of the site that leaves a request only partly read.
Only your developer or host can check these settings. Ask them for the PHP version, the date of the update and the settings named in the message below.
Why the October flaws make this more pressing
- The two October flaws, CVE-2026-109618 and CVE-2026-109619, are in the US government's CISA catalog of vulnerabilities that attackers exploit.
- Amazon reports an attempt to exploit them on 17 October 2026, four days before the fix was published. It later saw broad exploitation attempts.
- Qurium, a security organization, counted 15,557 suspicious requests from 89 IP addresses to 191 sites in the first week after disclosure. It found no proof that a complete attack succeeded.
- For the November flaws, Wiz had seen no attacks and no public reports of them when it published on 19 November. CISA's assessment of CVE-2026-115560 on 19 November also listed no exploitation.
Attackers already target PHP sites that were not updated in October. Ask whoever runs each site to confirm both updates, the October one and the November one.
How to know if your site is at risk
You do not need to read code. Answer three questions:
- Does the site run on PHP? WordPress, WooCommerce, PrestaShop, Magento, Drupal and Joomla all do. If you use a hosted website builder and never chose a server or hosting plan, the platform runs the servers; ask its support whether anything is needed from you.
- Who updates the server? It can be your hosting company, a web agency, a freelance developer or your own IT person. On shared hosting the host usually installs updates, but the PHP version is often a setting in your control panel. If that setting says 8.1 or older, it stays there until someone changes it.
- Which sites do you have? Count the old ones too: a test copy left online, a past campaign page, a site a former contractor still hosts. They are easy to overlook, so include them when you ask. Our PHP2Shell article lists where to look.
What to ask your developer or host today
Copy this message and send it to whoever runs each site. Replace the names in brackets.
Subject: PHP security updates of 19 November 2026
Hello [name],
On 19 November 2026 PHP released security fixes in versions 8.5.13, 8.4.28, 8.3.37 and 8.2.36, and the new 8.6.0. Seven of the flaws are rated Critical. For each of our websites and servers, please confirm in writing:
1. Which PHP version runs now, and the date it was updated to a fixed version (or to a hosting or distribution package that includes the fixes).
2. If a site runs PHP 8.1 or older: the PHP project no longer fixes these versions. Does our package receive backported fixes? What is the plan and the date to move to a supported version?
3. That PHP-FPM or the web server was restarted after the update, and container images were rebuilt.
4. That session.upload_progress.enabled is not switched on in php.ini, FPM pools, virtual hosts or .user.ini, unless we need it.
5. Whether the web server reuses FastCGI connections (nginx fastcgi_keep_conn, Apache enablereuse), and if so, whether any part of the site leaves php://input partly unread.
6. That the October fixes (CVE-2026-109618, CVE-2026-109619) are installed, and whether logs from 17 October onwards show anything unusual.
Thank you,
[your name]
A good reply names a version number and a date for each site. "We keep everything up to date" is not an answer you can check. If the reply says a site runs PHP 8.1 or older, ask for the cost and the date of the move to a supported version.
If your site runs PHP 8.1 or older
The PHP project no longer fixes these versions, so its updates do not reach them. Some hosting companies and Linux distributions backport fixes to old versions: ask yours whether it does so for these flaws. PHP 8.2 receives security fixes only until December 2026. Moving a site to a newer version can take your developer some testing, because old plugins or custom code may need changes. Plan it as a small project with a date, not as a task for some day.
What an outside check shows, and what it cannot
IntruForce specialists have prepared checks for these PHP flaws, and SeguriScan clients receive notifications.
An outside check shows what is reachable from the internet; it cannot see inside a server. From outside, a site sometimes reveals that it runs PHP and which version. It does not reveal the session settings or the code that decide whether these flaws can be used. That answer comes from your developer or hosting company.
New PHP flaws are tracked on our vulnerability radar, next to other software that small companies run on the internet.
Questions
- We use WordPress and update plugins. Are we covered? No. These flaws are in PHP itself, the software that runs WordPress. Updating WordPress, plugins or themes does not update PHP on the server.
- Our hosting company handles updates. Do we need to do anything? Ask them to confirm the PHP version of your site in writing. Also check the PHP version setting in your hosting control panel.
- Does an old PHP version mean we were hacked? No. It means the site misses fixes for known flaws. If the site also missed the October update, ask your developer to look at the server logs from 17 October 2026 onwards.
- What are the seven Critical flaws? According to Wiz: CVE-2026-129289, CVE-2026-126714, CVE-2026-115560, CVE-2026-129496, CVE-2026-129481, CVE-2026-129474 and CVE-2026-129182. Your developer will find the technical details in the sources below.
Sources
- PHP2Shell isn't over: 7 more Critical PHP bugs, cve.tools, 22 November 2026: the technical version, with commands to check a server and links to PHP, Wiz, Amazon and Qurium.
- Wiz: phpAfterShell and other critical PHP flaws, Wiz, 19 November 2026: the count of 17 flaws, the seven Critical ones, unsupported versions and the state of attacks.