Two days after the PHP2Shell emergency updates, PHP issued another warning. This flaw is real, but it needs a rare setup, and a single setting protects you.
- Date
- Reading
- 5 min read
- Written by
- Nick Li
- Tags
- #Risk#Web#Engineering
Two days after PHP's emergency PHP2Shell updates, the PHP project published another warning, this time about CVE-2026-115560. If you are hearing about yet another PHP flaw and starting to worry, take a breath: this one is real, but it is unlikely to affect your site, and the protection is a single setting.
What PHP announced
On 23 October, PHP published an informational advisory. The flaw could in theory let an attacker run code on a server, but only under an unusual combination of configuration and application code. PHP calls it an "unlikely RCE vector", so it has not released an emergency patch and will publish full details with its next regular release. So far, no attacks have been reported.
Who is affected
All three of these must be true:
- The site's PHP configuration sets
session.serialize_handlertophp_binaryorphp_serialize. - The application's code switches it back to
phpwithini_set()before it starts a session. - Session upload progress (
session.upload_progress.enabled) is still switched on, which is PHP's default.
Most WordPress sites, online shops and company websites never change this setting at runtime, so they are not exposed. Note that the PHP2Shell updates (8.5.12, 8.4.27, 8.3.36 and 8.2.35) do not include this fix. If your code does match the conditions above, being up to date is not enough on its own.
The fix: one line in php.ini
PHP recommends switching off session upload progress until its next release:
session.upload_progress.enabled = 0
This is the same setting PHP listed as a temporary protection for PHP2Shell on 21 October. If your team applied it then, you are already covered and nothing else is needed.
Where the line goes depends on your hosting:
- Your own server or VPS: add it to
php.ini(or the PHP-FPM pool configuration), then restart PHP-FPM or the web server. - Shared hosting with cPanel: use the MultiPHP INI Editor, or add the line to a
.user.inifile in the site's root folder. - Managed WordPress hosting: ask your provider. Many manage PHP settings for you.
This setting cannot be changed from code with ini_set(); it has to go in the configuration. The only side effect is that PHP's built-in tracking of file-upload progress stops working. Few sites rely on it, but if yours shows a progress bar when uploading files, test it after the change.
How your developer can check in two minutes
- Confirm the setting is applied: on a
phpinfo()page, the session section should showsession.upload_progress.enabledasOff. The command-linephp -ican read a different configuration, so trust the web page, and delete it when you are done. - Search the code: run
grep -rn "serialize_handler" .in the site's folder. If nothing changes it withini_set, this flaw does not apply to you.
Keep it in perspective
Two PHP warnings in one week sounds alarming, but they are very different. PHP2Shell is critical and already being attacked, so update now. CVE-2026-115560 is unlikely to apply to you, and one setting closes it while PHP prepares the full fix.
Not every security headline is an emergency. The useful questions are: does it apply to us, and what is the smallest safe step?
If you are not sure how your website is configured, or would like someone to check it for you, get in touch.
